Symptom
- The event ASSIGNED is not generated for an object when it expected
OR - Dump OS_COMMIT_TOP_FAILED raised when working with Business documents (storing, assigning, displaying, using barcode scenario)
Read more...
Environment
Check the detailed environmental information for the specific SAP notes.
Keywords
ARCHIV_CONNECTION_INSERT, ARCHIV_WFL_LATE, CL_ALINK_STORAGE_DND, STORE_WITH_KEY, CL_ARL_SRV_LINK, EXECUTE, ARCHIV_ASSIGN_DOCUMENT, CL_WF_SRV_OVERVIEW, COMMIT_IN_POSTING, OAWD,SBWP,<Object>.assigned,LINK.ASSIGNED, Event <Object>.assigned is not triggered, BDSBARCOM,Commit work, barcode, archiv_connection_insert, OAWD,SBWP,<Object>.assigned,LINK.ASSIGNED, Event <Object>.assigned is not triggered, Assign event, archive link, work flow, late assignment, commit work, GOS,Drag and drop,<Object>.assigned,display/change transactions, Generic Object Services,ALINK.ASSIGNED,Generate Event <Object>.assigned,OAG1 , KBA , commit_in_posting , archiv_connection_insert , oaad , bdsbarcom , store business document , oag1 , gos , commit work , document viewer , BC-SRV-ARL , ArchiveLink , BC-BMT-WFM , Business Workflow , BC-SRV-GBT-GOS , Generic Object Services , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.