{"count":6,"articles":[{"id":"guest-knowledge-sd-pricing","module_key":"sd","module_name":"Sales and Distribution","question":"Pricing missing in sales order","answer":"Start with pricing analysis, confirm the pricing procedure, and verify condition-record validity before retrying the order.","symptom":"Pricing conditions do not appear during order creation.","probable_root_causes":["Missing condition records","Pricing procedure assignment gap"],"diagnostic_steps":["Check pricing analysis in VA01 or VA02","Review the condition type access sequence","Confirm customer and sales-area master data"],"resolution_steps":["Maintain the missing record in VK11","Reprice the order after correcting the procedure assignment"],"related_tcodes":["VA01","VA02","VK11"],"related_tables":["VBAK","VBAP","KONV"],"config_paths":["SPRO > Sales and Distribution > Basic Functions > Pricing"],"keywords":["pricing","sales order","condition record"],"support_angle":"module-playbook","score":0.8,"source_kind":"module_playbook","process_area":"order-to-cash","error_type":"pricing","integration_topic":"module-local troubleshooting","business_context":"Sales and Distribution support issue affecting order-to-cash.","test_scenario":"Reproduce the symptom in VA01 using the same organizational data and compare against a known-good Sales and Distribution example.","common_mistakes":"Teams often retry the transaction before correcting the underlying issue: Missing condition records.","key_fields":{"VBAK":["VBELN","AUART","VKORG"],"VBAP":["VBELN","POSNR","MATNR"],"KONV":["CLIENT","REFERENCE_ID","CHANGED_ON"]},"related_dependencies":["Validate upstream processing in VA01.","Check persistence consistency in VBAK.","Review customizing path SPRO > Sales and Distribution > Basic Functions > Pricing."],"linked_modules":["fi"]},{"id":"guest-knowledge-mm-invoice","module_key":"mm","module_name":"Materials Management","question":"MIRO invoice blocked","answer":"Review the blocking reason, then compare the invoice against PO history, tolerance settings, and GR or IR balance details.","symptom":"Invoice verification stops with a blocking or tolerance message.","probable_root_causes":["Tolerance breach","PO or GR mismatch"],"diagnostic_steps":["Inspect the MIRO blocking reason","Compare PO quantity, GR quantity, and invoice amount","Check vendor and tolerance customizing"],"resolution_steps":["Correct the upstream quantity or price mismatch","Repost after the tolerance issue is resolved"],"related_tcodes":["MIRO","ME23N","MRBR"],"related_tables":["RBKP","RSEG","EKPO"],"config_paths":["SPRO > Materials Management > Logistics Invoice Verification"],"keywords":["miro","invoice","tolerance"],"support_angle":"module-playbook","score":0.79,"source_kind":"module_playbook","process_area":"procure-to-pay","error_type":"invoice","integration_topic":"module-local troubleshooting","business_context":"Materials Management support issue affecting procure-to-pay.","test_scenario":"Reproduce the symptom in MIRO using the same organizational data and compare against a known-good Materials Management example.","common_mistakes":"Teams often retry the transaction before correcting the underlying issue: Tolerance breach.","key_fields":{"RBKP":["DOC_NUMBER","ITEM_NUMBER","REFERENCE_KEY"],"RSEG":["CLIENT","REFERENCE_ID","CHANGED_ON"],"EKPO":["EBELN","EBELP","MATNR"]},"related_dependencies":["Validate upstream processing in MIRO.","Check persistence consistency in RBKP.","Review customizing path SPRO > Materials Management > Logistics Invoice Verification."],"linked_modules":["fi"]},{"id":"guest-knowledge-fi-period","module_key":"fi","module_name":"Financial Accounting","question":"Posting period closed in FI","answer":"Validate the company code, account type, and posting period variant before reopening the correct period in a controlled way.","symptom":"Accounting posting fails because the period is not open.","probable_root_causes":["Closed posting period","Wrong account type or company-code variant"],"diagnostic_steps":["Capture the exact posting date and company code","Check OB52 for the relevant account type","Verify whether special periods are in use"],"resolution_steps":["Open the correct period in OB52","Retest the posting in QA before production correction"],"related_tcodes":["OB52","FB50","FB01"],"related_tables":["T001B","BKPF","BSEG"],"config_paths":["SPRO > Financial Accounting > Financial Accounting Global Settings > Document > Posting Periods"],"keywords":["posting period","ob52","finance"],"support_angle":"module-playbook","score":0.78,"source_kind":"module_playbook","process_area":"record-to-report","error_type":"posting","integration_topic":"module-local troubleshooting","business_context":"Financial Accounting support issue affecting record-to-report.","test_scenario":"Reproduce the symptom in OB52 using the same organizational data and compare against a known-good Financial Accounting example.","common_mistakes":"Teams often retry the transaction before correcting the underlying issue: Closed posting period.","key_fields":{"T001B":["BUKRS","MONAT","GJAHR"],"BKPF":["BELNR","BUKRS","GJAHR"],"BSEG":["BELNR","BUZEI","HKONT"]},"related_dependencies":["Validate upstream processing in OB52.","Check persistence consistency in T001B.","Review customizing path SPRO > Financial Accounting > Financial Accounting Global Settings > Document > Posting Periods."],"linked_modules":[]},{"id":"guest-knowledge-pp-confirmation","module_key":"pp","module_name":"Production Planning","question":"Production order confirmation error","answer":"Check the order status, operation confirmation controls, and any backflush or work-center dependencies before reposting the confirmation.","symptom":"Order confirmation fails during manufacturing execution.","probable_root_causes":["Order status mismatch","Operation-control issue"],"diagnostic_steps":["Review the order and operation status","Check confirmation parameters and backflush settings","Inspect related goods movement errors"],"resolution_steps":["Correct the operation status or missing master data","Reconfirm after resolving dependent movement errors"],"related_tcodes":["CO11N","CO02","MF47"],"related_tables":["AFKO","AFVC","AFRU"],"config_paths":["SPRO > Production > Shop Floor Control > Operations"],"keywords":["production order","confirmation","shop floor"],"support_angle":"module-playbook","score":0.77,"source_kind":"module_playbook","process_area":"production execution","error_type":"posting","integration_topic":"module-local troubleshooting","business_context":"Production Planning support issue affecting production execution.","test_scenario":"Reproduce the symptom in CO11N using the same organizational data and compare against a known-good Production Planning example.","common_mistakes":"Teams often retry the transaction before correcting the underlying issue: Order status mismatch.","key_fields":{"AFKO":["AUFNR","AUART","PLNBEZ"],"AFVC":["AUFPL","APLZL","VORNR"],"AFRU":["CLIENT","REFERENCE_ID","CHANGED_ON"]},"related_dependencies":["Validate upstream processing in CO11N.","Check persistence consistency in AFKO.","Review customizing path SPRO > Production > Shop Floor Control > Operations."],"linked_modules":["sd","fi"]},{"id":"guest-knowledge-basis-transport","module_key":"basis","module_name":"Basis / Technical Support","question":"Transport import created regression","answer":"Review the import queue, object versions, activation state, and follow-up jobs before assuming the issue is purely functional.","symptom":"A regression appears after a transport or support-package movement.","probable_root_causes":["Inactive object after import","Object version mismatch"],"diagnostic_steps":["Check the transport import logs","Compare object versions across systems","Validate activation and dependent jobs"],"resolution_steps":["Reactivate or reimport the affected object set","Retest the impacted business flow after activation"],"related_tcodes":["STMS","SE09","SE10"],"related_tables":["E070","E071","TRBAT"],"config_paths":["STMS import queue and transport governance"],"keywords":["transport","basis","import"],"support_angle":"module-playbook","score":0.76,"source_kind":"module_playbook","process_area":"platform operations","error_type":"general_support","integration_topic":"module-local troubleshooting","business_context":"Basis / Technical Support support issue affecting platform operations.","test_scenario":"Reproduce the symptom in STMS using the same organizational data and compare against a known-good Basis / Technical Support example.","common_mistakes":"Teams often retry the transaction before correcting the underlying issue: Inactive object after import.","key_fields":{"E070":["CLIENT","REFERENCE_ID","CHANGED_ON"],"E071":["CLIENT","REFERENCE_ID","CHANGED_ON"],"TRBAT":["CLIENT","REFERENCE_ID","CHANGED_ON"]},"related_dependencies":["Validate upstream processing in STMS.","Check persistence consistency in E070.","Review customizing path STMS import queue and transport governance."],"linked_modules":["fi"]},{"id":"guest-knowledge-cross-interface","module_key":"cross_module","module_name":"Cross-Module Integration","question":"Interface handoff failed between modules","answer":"Trace the message or IDoc lifecycle first, then confirm the sender business document, receiver status, and reprocessing path.","symptom":"A cross-module or external handoff stops before the downstream document is created.","probable_root_causes":["IDoc status failure","Receiver-side validation error"],"diagnostic_steps":["Review the message status and payload","Check sender and receiver document numbers","Inspect reprocessing options"],"resolution_steps":["Fix the failing segment or receiver validation issue","Reprocess the message after confirming end-to-end consistency"],"related_tcodes":["WE02","WE05","BD87"],"related_tables":["EDIDC","EDIDS","ARFCSDATA"],"config_paths":["ALE / IDoc monitoring and reprocessing"],"keywords":["interface","idoc","handoff"],"support_angle":"module-playbook","score":0.75,"source_kind":"module_playbook","process_area":"cross-module integration","error_type":"posting","integration_topic":"system integration","business_context":"Cross-Module Integration support issue affecting cross-module integration.","test_scenario":"Reproduce the symptom in WE02 using the same organizational data and compare against a known-good Cross-Module Integration example.","common_mistakes":"Teams often retry the transaction before correcting the underlying issue: IDoc status failure.","key_fields":{"EDIDC":["DOCNUM","MESTYP","STATUS"],"EDIDS":["DOCNUM","STATUS","LOGDAT"],"ARFCSDATA":["CLIENT","REFERENCE_ID","CHANGED_ON"]},"related_dependencies":["Validate upstream processing in WE02.","Check persistence consistency in EDIDC.","Review customizing path ALE / IDoc monitoring and reprocessing."],"linked_modules":["sd","mm","fi"]}]}