#AI-Generated Content
Hello,
Thank you very much for your question.
I've asked our internal AI tool for support, and here's the response. Please check whether the suggestions work for you.
Kind regards,
Henrike
Here is the guidance tailored specifically to SAP S/4HANA Cloud Public Edition with embedded EWM.
Key Public Edition Specifics You Need to Know
BIDF Is an Internal Process Code, Not a Deliverable Exception Code
This is the most important thing to understand for your situation, and it is documented in SAP KBA 3564528:
In SAP S/4HANA Cloud Public Edition, BIDF and BIDP are not delivered as exception codes. They are delivered as internal process codes only.
This means you cannot simply use BIDF directly as your exception code. Instead, you must create a custom exception code (e.g., ZIDF) and assign BIDF as its internal process code. What you see in the Define Exception Codes SSCUI is BIDF in the value help for internal process codes, not as a selectable exception code itself.
Configuration Path in S/4HANA Cloud Public Edition
All exception handling configuration is done via the Business Configuration work center (previously Central Business Configurator), not via SPRO.
Step 1 — Define Your Exception Code
SSCUI: 104743 – Define Exception Codes
Create a custom exception code (e.g., ZIDF) and assign:
Field Value
| Business Context | TPI – Confirm Warehouse Task (Stock Removal) |
| Execution Step | 05 – Product WT on Source Storage Bin (RF picking) |
| Internal Process Code | BIDF |
If your pickers are confirming via the Confirm Warehouse Tasks - Advanced Fiori app rather than RF, also add the assignment for execution step 02 (desktop). Without this, the exception code will simply not appear during confirmation.
Step 2 — Activate Pick Denial at Warehouse Level
Pick denial must be explicitly activated for your warehouse number. Without this switch, the BIDF internal process code will not trigger a new source bin determination even if everything else is configured correctly.
Look for the pick denial activation setting within the EWM warehouse configuration in Business Configuration — it corresponds to the IMG activity Goods Issue Process → Pick Denial → Activate Pick Denial at Warehouse Number Level.
Step 3 — Activate Pick Denial at Warehouse Process Type Level
In the Define Warehouse Process Types configuration (also accessible via Business Configuration), locate your WPT and set the Pick Denial control indicator. This tells the system that pick denial is permitted for this specific process type.
Step 4 — Assign the Exception Code to the WPT
Your custom exception code (ZIDF) must be included in the exception code list assigned to your WPT. Without this assignment, the code will not be selectable during RF or Fiori picking confirmation.
Step 5 — Assign Users to the Exception Code Profile
Use the Fiori app Assign Users to Exception Code Profiles to ensure the warehouse workers who need to use this exception have the correct profile assigned for the relevant warehouse number.
Additional Checks If It Still Does Not Work
Check What to Verify
| Product WT vs. HU WT | BIDF is not allowed for HU warehouse tasks (KBA 2768467). Your picking process must create product WTs. |
| Confirmation app | Exception codes for picking are only available in the Confirm Warehouse Tasks - Advanced app (KBA 3069905). Standard Process Warehouse Task – Picking (F3880) does not expose exception codes. |
| Alternate stock exists | The system needs to find available stock in another bin via the storage type search sequence. If no alternative exists, no new WT is created — a physical inventory document may be triggered instead. |
| SPC/WMR restriction | If the WT originates from a posting change (SPC) or warehouse management request (WMR), BIDF will not create a new WT — this is a known SAP limitation (KBA 2755011). |
| Source bin field editable | The source bin cannot be directly edited in the Fiori picking app (KBA 3586252) — the re-determination happens automatically through the exception code flow, not via manual field input. |
Summary of the Most Likely Root Cause
Based on what you've described, the most probable reason BIDF is not working is one of the following:
- You defined BIDF as the exception code itself rather than creating a custom code with BIDF as the internal process code — this is the KBA 3564528 issue specific to Public Edition.
- Pick denial is not activated at the warehouse number or WPT level.
- The exception code is not being triggered via the correct app (must be Confirm Warehouse Tasks - Advanced).
Check these three points first, and the behavior should work as expected.
Bluesky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.