服务条目表(SES)Release group与Release Strategy字段未填充及ML81N/ML85事务码新订单未分配审批策略问题求助

Hey Diego, let's break down the two related issues you're hitting with Service Entry Sheets (SES) and their release procedures—since you’ve already walked through the standard config steps, here are some often-missed checks that could be causing the problem:

1. Double-Check Classification & Characteristic Setup #

• First, verify your CT04 characteristic RILASCIOPRESTAZIONI:
  • Make sure its data type and value range align with the conditions you set in your release strategy. For example, if you’re using monetary thresholds, the characteristic should be a numeric type, and the strategy’s classification intervals must cover the exact value of your new SES.
  • Confirm in CL02 that this characteristic is correctly assigned to the class RILASCIOPRESTAZION, and that the class is linked to the SES object type (BUS2012) in the Object Types tab of the class maintenance.
• In OLMSRV → Release Strategies → Classification, ensure each strategy’s characteristic values match the attributes of your SES exactly. For instance, if your release group is Z1, the characteristic value assigned to the strategy should be Z1—no typos or mismatches here!

2. Validate Release Procedure Configuration #

• Navigate to OLMSRV → Define Release Procedure for Service Entry Sheet → Release Procedures (the top-level procedure definition, not individual strategies). Check that your release group Z1 is assigned to an active procedure, and that the procedure’s Release Requirements (if configured) don’t include unintended conditions that block strategy assignment.
• Verify the Release Indicator settings: Ensure the "Released" indicator is correctly linked to your release codes, and that the indicator allows further processing once released (if that’s your requirement).

3. Verify SES Header Field Matching #

• When creating a new SES in ML81N or ML85, cross-check header fields against your release strategy’s classification conditions:
  • Key fields like Purchasing Organization, Purchasing Group, and Company Code must match exactly what’s defined in your strategy’s classification. Even a single mismatched value will prevent the strategy from triggering.
  • Confirm the SES’s total value (or whatever key metric you’re using to trigger the strategy) meets or exceeds the threshold set in your release strategy. If the value falls below the minimum interval, no strategy will be assigned.

4. Clear SAP Buffers & Sync Master Data #

• Classification data can get stuck in SAP’s buffer, leading to outdated or missing strategy assignments. Try running the program RCLCTDEL via SE38 to clear classification buffers, then log out and back in before testing again.
• If you’ve recently made config changes, ensure you’ve generated the release strategy correctly in OLMSRV → Release Strategies—look for the "Generate" button to refresh strategy assignments.

5. Check User Permissions & Transaction Defaults #

• Confirm your user has the M_SRV_REL authorization object assigned, with permissions for release group Z1 and release code Z1. Missing permissions can sometimes cause the strategy to fail to load silently (without an error message).
• In ML81N, ensure you’re not using a template that’s set to bypass release procedures. You can check this by creating a SES from scratch instead of using a template.

内容的提问来源于stack exchange，提问作者Diego