{"audience":"Shift supervisors, production planners and PP consultants in plants with or without an MES integration.","authorization_objects":[{"note":"Authorization to enter confirmations by plant and order type","object":"C_AFRU_AWK"}],"components":[],"countries":[],"effort_days_max":6,"effort_days_min":4,"effort_size":"M","faq":[{"a":"Yes. The BAPI uses the same confirmation logic as CO11N; backflush defined on the operation and automatic goods receipt on the last operation run as standard. Movements that fail go to COGI and are shown in the result list.","q":"Do backflush and automatic goods receipt run as well?"},{"a":"Yes. Files that MES drops into a folder on the application server are processed periodically by a background job; processed files are moved to an archive folder.","q":"Can the file come automatically from MES?"},{"a":"Yes. BAPI_PRODORDCONF_CREATE_TT is supported on S/4HANA as well; backflush writes material documents to MATDOC.","q":"Can it be used on S/4HANA?"}],"features":[{"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":"Failed rows can be corrected and uploaded again with the same template."},{"code":"excel","label":"Export to Excel","note":"An empty upload template can be downloaded as Excel."},{"code":"background","label":"Runs as a background job","note":"MES files can be processed periodically from a folder on the application server."}],"functions":[{"name":"BAPI_PRODORDCONF_CREATE_TT","role":"Creates the operation confirmation as a time ticket for each row"},{"name":"BAPI_TRANSACTION_COMMIT","role":"Saves successful rows permanently"},{"name":"BAPI_TRANSACTION_ROLLBACK","role":"Rolls back the changes of a failed row"}],"gap":"CO11N confirms one operation on screen; CO12 is a collective entry screen but does not read files. Entering hundreds of confirmations by hand at the end of a shift takes time and increases the risk of wrong quantities and duplicate records. A full MES interface is not needed in every plant; a file-based upload with a test mode covers most needs.","id":"pp-confirmation-upload","industries":[],"input_columns":[{"derived":false,"label":"Production order","required":true,"rule":"","target_field":"AUFNR","target_table":"AFRU"},{"derived":false,"label":"Operation","required":true,"rule":"","target_field":"VORNR","target_table":"AFRU"},{"derived":false,"label":"Posting date","required":false,"rule":"","target_field":"BUDAT","target_table":"AFRU"},{"derived":false,"label":"Yield","required":true,"rule":"","target_field":"LMNGA","target_table":"AFRU"},{"derived":false,"label":"Scrap","required":false,"rule":"","target_field":"XMNGA","target_table":"AFRU"},{"derived":false,"label":"Rework","required":false,"rule":"","target_field":"RMNGA","target_table":"AFRU"},{"derived":false,"label":"Variance reason","required":false,"rule":"","target_field":"GRUND","target_table":"AFRU"},{"derived":false,"label":"Setup time (h)","required":false,"rule":"","target_field":"ISM01","target_table":"AFRU"},{"derived":false,"label":"Machine time (h)","required":false,"rule":"","target_field":"ISM02","target_table":"AFRU"},{"derived":false,"label":"Labor time (h)","required":false,"rule":"","target_field":"ISM03","target_table":"AFRU"},{"derived":false,"label":"Final confirmation (X)","required":false,"rule":"","target_field":"AUERU","target_table":"AFRU"},{"derived":false,"label":"Personnel number","required":false,"rule":"","target_field":"PERNR","target_table":"AFRU"}],"kind":"program","language":"en","lastmod":"2026-11-17","logic":"1. The file (XLSX or CSV) is read from the user's PC or, in a background job, from a folder on the application server; the first row is skipped as the header.\n2. Every row is checked: the order exists in AFKO, is released (REL) and not technically completed; the operation number exists in AFVC and its control key allows confirmation; the variance reason and personnel number are valid when filled.\n3. Duplicate check: if AFRU already has a non-cancelled confirmation (STOKZ blank) with the same order, operation, posting date, personnel number and yield, the row is stopped with a warning.\n4. The row is mapped to the time ticket structure of BAPI_PRODORDCONF_CREATE_TT: yield, scrap, rework, variance reason, setup/machine/labor activities, final confirmation and personnel number. When the posting date is blank, the default date from the selection screen is used.\n5. In test mode the BAPI is called as a test run; confirmation and backflush are checked without posting.\n6. In a real run BAPI_TRANSACTION_COMMIT is called after every successful row and BAPI_TRANSACTION_ROLLBACK after an error. The confirmation number (RUECK/RMZHL) and messages are listed. Goods movements that fail during backflush are written to AFFW (COGI) as standard; this is shown on the row as well.","module":"PP","object_type":"upload","output_columns":[{"calculated":true,"formula":"Row number in the file","label":"Row","source_field":null,"source_table":null},{"calculated":false,"formula":"","label":"Production order","source_field":"AUFNR","source_table":"AFRU"},{"calculated":false,"formula":"","label":"Operation","source_field":"VORNR","source_table":"AFRU"},{"calculated":true,"formula":"AFRU-RUECK / AFRU-RMZHL returned by the BAPI","label":"Confirmation no.","source_field":null,"source_table":null},{"calculated":true,"formula":"From the BAPI return messages: posted, posted (COGI) or error","label":"Status","source_field":null,"source_table":null},{"calculated":true,"formula":"First error or success message from the BAPI return table","label":"Message","source_field":null,"source_table":null}],"parameters":[{"example":"C:\\temp\\vardiya_teyit.xlsx","kind":"parameter","label":"Confirmation file (XLSX or CSV)","name":"P_FILE","ref_field":"","required":true},{"example":"16.11.2026","kind":"parameter","label":"Default posting date (when blank in the file)","name":"P_BUDAT","ref_field":"AFRU-BUDAT","required":false},{"example":"X","kind":"checkbox","label":"Test mode (check without posting)","name":"P_TEST","ref_field":"","required":false},{"example":"X","kind":"checkbox","label":"Duplicate confirmation check","name":"P_CHKDUP","ref_field":"","required":false}],"part_of":[],"performance":"Run files above a few thousand rows as a background job. Committing per row isolates failed rows; processing the rows of the same order one after another avoids lock conflicts.","quote_url":"https://nekuhub.com/en/request-a-quote/?report=pp-confirmation-upload","related":["pp-cogi-failed-goods-movements-aging","pp-scrap-yield-by-work-center"],"releases":[],"source":"custom","standard_alternatives":[{"note":"Confirms one operation on screen; does not read files.","tcode":"CO11N"},{"note":"A collective entry screen; rows are still entered by hand and there is no duplicate check.","tcode":"CO12"}],"summary":"A custom program that reads operation confirmations (yield, scrap, rework, activity times) coming from MES, shop-floor terminals or Excel at the end of a shift and posts them to production orders in bulk. It checks everything in test mode first, stops duplicate confirmations and lists the result of every row.","tables":[{"access":"write","join_on":"","role":"Posted confirmations; also read for the duplicate check","table":"AFRU","variant":"both"},{"access":"read","join_on":"","role":"Order header and routing number (AUFPL)","table":"AFKO","variant":"both"},{"access":"read","join_on":"","role":"Operation number, control key and work center","table":"AFVC","variant":"both"},{"access":"write","join_on":"","role":"Goods movements that fail during backflush (written as standard)","table":"AFFW","variant":"both"}],"title":"Mass Production Order Confirmation Upload Program","url":"https://nekuhub.com/en/programs/mass-production-order-confirmation-upload-program/","vendor_id":"nekudos"}