{"audience":"Production planners, MRP controllers and shop floor supervisors who manage order release before the shift.","authorization_objects":[{"note":"Authorization to release orders by plant and order type","object":"C_AFKO_AWK"},{"note":"Production order authorization by MRP controller","object":"C_AFKO_DIS"}],"components":[],"countries":[],"effort_days_max":6,"effort_days_min":4,"effort_size":"M","faq":[{"a":"No. The program applies its own threshold before release; the standard availability check defined for the order type still runs during the BAPI call. The two checks complement each other.","q":"Does it replace the standard availability check?"},{"a":"Yes. The threshold can be read from the selection screen or from a small settings table by plant / order type. A separate background variant can also be defined for each plant.","q":"Can the threshold differ by plant?"},{"a":"The base version only counts unrestricted stock on hand. If required, open purchase order schedule lines (EKET) due before the start date can be added as a coverage source.","q":"Are open purchase orders taken into account?"}],"features":[{"code":"test_run","label":"Test mode (check without posting)","note":""},{"code":"log","label":"Line-by-line result and error log","note":""},{"code":"background","label":"Runs as a background job","note":"Scheduled as a background job every night or before the shift."},{"code":"email","label":"Send the result by email","note":"The list of released and held orders is sent to each MRP controller."}],"functions":[{"name":"BAPI_PRODORD_RELEASE","role":"Releases the orders that pass the threshold"},{"name":"BAPI_TRANSACTION_COMMIT","role":"Saves the status change permanently"}],"gap":"COHV releases the selected orders in mass and can run an availability check depending on the order type settings, but the check follows a general rule such as 'do not release if missing' or 'release anyway'. A plant-specific threshold (for example, release when 90 percent of the components are covered) or a critical component exception cannot be defined. Planners filter the list by hand every morning; as a result either orders with shortages reach the shop floor or ready orders stay on hold.","id":"pp-mass-release-with-component-check","industries":[],"input_columns":[],"kind":"program","language":"en","lastmod":"2026-11-17","logic":"1. Orders whose scheduled start (GSTRP) falls within the release horizon from today are read from AUFK and AFKO for the plant, order type and MRP controller on the selection screen; only orders with just the created status (I0001) active in JEST and no deletion flag (I0076) become candidates.\n2. The component requirements of the candidates are read from RESB; bulk (SCHGT) and phantom (DUMPS) items are left out.\n3. Unrestricted stock is read from MARD-LABST and requirements are sorted by start date and allocated in turn, so the order that starts earlier gets the stock first.\n4. Coverage = components covered by stock ÷ all components × 100. When coverage is below the threshold, or a component from the critical component list is missing, the order is skipped and the allocated stock is left for the next order.\n5. Orders above the threshold are released in packages with BAPI_PRODORD_RELEASE and BAPI_TRANSACTION_COMMIT is called; return messages are logged per order.\n6. In test mode no order is released; only the candidate list and the decisions are shown. Optionally the result list is emailed to the MRP controllers.","module":"PP","object_type":"batch_job","output_columns":[{"calculated":false,"formula":"","label":"Production order","source_field":"AUFNR","source_table":"AFKO"},{"calculated":false,"formula":"","label":"Material","source_field":"PLNBEZ","source_table":"AFKO"},{"calculated":false,"formula":"","label":"Scheduled start","source_field":"GSTRP","source_table":"AFKO"},{"calculated":false,"formula":"","label":"MRP controller","source_field":"DISPO","source_table":"AFKO"},{"calculated":true,"formula":"Number of evaluated RESB items","label":"Components","source_field":null,"source_table":null},{"calculated":true,"formula":"Number of items not covered by the allocated stock","label":"Short components","source_field":null,"source_table":null},{"calculated":true,"formula":"(Components − short components) ÷ components × 100","label":"Coverage %","source_field":null,"source_table":null},{"calculated":true,"formula":"Released, candidate (test), below threshold or critical component short","label":"Result","source_field":null,"source_table":null},{"calculated":true,"formula":"BAPI return message or reason for skipping","label":"Message","source_field":null,"source_table":null}],"parameters":[{"example":"1000","kind":"select_option","label":"Plant","name":"S_WERKS","ref_field":"AUFK-WERKS","required":true},{"example":"PP01","kind":"select_option","label":"Order type","name":"S_AUART","ref_field":"AUFK-AUART","required":false},{"example":"001","kind":"select_option","label":"MRP controller","name":"S_DISPO","ref_field":"AFKO-DISPO","required":false},{"example":"3","kind":"parameter","label":"Release horizon (days)","name":"P_HORIZ","ref_field":"","required":true},{"example":"90","kind":"parameter","label":"Component coverage threshold (%)","name":"P_THRESH","ref_field":"","required":true},{"example":"RM-3220","kind":"select_option","label":"Critical components (never release when short)","name":"S_CRIT","ref_field":"RESB-MATNR","required":false},{"example":"X","kind":"checkbox","label":"Test mode (candidate list only)","name":"P_TEST","ref_field":"","required":false}],"part_of":[],"performance":"Limit the candidates with the start date horizon and read RESB and MARD once. Releasing in packages of 50–100 orders reduces lock problems. The program is usually scheduled every night or one hour before the shift starts.","quote_url":"https://nekuhub.com/en/request-a-quote/?report=pp-mass-release-with-component-check","related":["pp-missing-parts-with-covering-po","pp-planned-order-conversion-readiness"],"releases":[],"source":"custom","standard_alternatives":[{"note":"Releases orders in mass; there is no plant-specific coverage threshold or critical component exception.","tcode":"COHV"}],"summary":"A custom background program that automatically releases production orders whose scheduled start is approaching, when the share of components covered by stock exceeds a plant-specific threshold. Orders below the threshold are not released and are reported to planning with the number of missing components.","tables":[{"access":"read","join_on":"","role":"Order type, plant and object number","table":"AUFK","variant":"both"},{"access":"read","join_on":"AFKO-AUFNR = AUFK-AUFNR","role":"Scheduled start and MRP controller","table":"AFKO","variant":"both"},{"access":"read","join_on":"RESB-AUFNR = AFKO-AUFNR","role":"Component requirements of the order","table":"RESB","variant":"both"},{"access":"read","join_on":"MARD-MATNR = RESB-MATNR AND MARD-WERKS = RESB-WERKS","role":"Unrestricted-use stock of the components","table":"MARD","variant":"both"},{"access":"write","join_on":"JEST-OBJNR = AUFK-OBJNR","role":"System status; release (I0002) is set through the BAPI","table":"JEST","variant":"both"}],"title":"Mass Production Order Release with Component Availability Check Program","url":"https://nekuhub.com/en/programs/mass-production-order-release-with-component-check/","vendor_id":"nekudos"}