What problem does it solve? ERP implementation consultants often mistake standard K/3 Cloud functionality for customization requirements, wasting effort on BOS extensions or Python plugins for features the product already ships. This Skill provides a module-organized index of standard features with enablement paths and common misjudgment cases, so consultants can check whether a requirement is already covered before recommending secondary development. ## Core Features & Use Cases - Module-organized feature dictionaries: Ten reference files covering SAL (sales), PUR (procurement), STK (inventory), FIN (finance AR/AP/GL), BD (base data), MFG (manufacturing), MRP (planning), FA (fixed assets), CB (cash/treasury), and reporting/BI, each listing standard functions with enablement paths. - Misjudgment tables: Each module file includes a "thought it needed customization" summary mapping typical consultant requests to the actual standard feature and its menu path. - Completeness grading: Entries are marked as verified, main-flow-only, or skeleton, with explicit instructions not to give enablement paths from skeleton-level entries. - Use Case: A client asks to "add automatic customer code generation." Load the BD reference, find that the standard coding-rule feature covers it, and give the user the enablement path instead of writing a plugin. ## Quick Start Load this skill and ask whether the client's requirement to automatically generate document numbers by date and sequence is a standard K/3 Cloud feature or needs customization.
