5
!a11y> SRM Business Workflow Use In the SRM Server ( Enterprise Buyer [EBP] and SAP Bidding Engine) a range of business transactions are based on workflow processes. Some workflows are absolutely essential for SRM whilst others can be used on an optional basis. Some are also provided as alternatives to others. The following (standard) workflows support SRM basic processes: Workflow for: Scenario Shopping cart (SC) WS10000060 – Without approval, WS10000129 – Onestep approval, WS10000031 – Twostep approval Approval workflows for shopping carts The relevant approval workflow is started, depending on the total value of the shopping cart and the role of the requester. Confirmation (CF) WS10400010 – Without approval, WS10400002 – Onestep approval, WS10400009 – Twostep approval, WS10400020 – Administrator approval Approval workflows for confirmations The relevant approval workflow is started, depending on completion status, creator role, and total value of the confirmation. Invoice (IV) WS10400016 – Without approval, WS10400017 – Onestep approval, WS10400018 – Twostep approval, WS10400021 – Administrator approval Approval workflows for invoices The relevant approval workflow is started, depending on completion status, invoice category (credit memo or invoice), creator role, and total value of the invoice. Purchase order (PO)

SRM Business Workflow - Architecture and Technology - SAP Library

Embed Size (px)

DESCRIPTION

SRM Business Workflow - Architecture and Technology - SAP Library

Citation preview

  • 27/5/2015 SRMBusinessWorkflowArchitectureandTechnologySAPLibrary

    http://help.sap.de/saphelp_srm40/helpdata/en/8b/4fa9585db211d2b404006094b92d37/content.htm?frameset=/en/8b/4fa9585db211d2b404006094b92d37/frameset.htm&current_toc=/en/d6/4def8242df214aa27644e41da65d07/plain.ht 1/5

    !a11y>

    SRMBusinessWorkflow

    UseInthe SRMServer ( EnterpriseBuyer [EBP]andSAPBiddingEngine) arangeofbusinesstransactionsarebasedonworkflowprocesses.SomeworkflowsareabsolutelyessentialforSRMwhilstotherscanbeusedonanoptionalbasis.Somearealsoprovidedasalternativestoothers.

    Thefollowing(standard)workflowssupportSRMbasicprocesses:

    Workflowfor: Scenario

    Shoppingcart(SC)WS10000060Withoutapproval,WS10000129Onestepapproval,WS10000031Twostepapproval

    ApprovalworkflowsforshoppingcartsTherelevantapprovalworkflowisstarted,dependingonthetotalvalueoftheshoppingcartandtheroleoftherequester.

    Confirmation(CF)WS10400010Withoutapproval,WS10400002Onestepapproval,WS10400009Twostepapproval,WS10400020Administratorapproval

    ApprovalworkflowsforconfirmationsTherelevantapprovalworkflowisstarted,dependingoncompletionstatus,creatorrole,andtotalvalueoftheconfirmation.

    Invoice(IV)WS10400016Withoutapproval,WS10400017Onestepapproval,WS10400018Twostepapproval,WS10400021Administratorapproval

    ApprovalworkflowsforinvoicesTherelevantapprovalworkflowisstarted,dependingoncompletionstatus,invoicecategory(creditmemoorinvoice),creatorrole,andtotalvalueoftheinvoice.

    Purchaseorder(PO)

  • 27/5/2015 SRMBusinessWorkflowArchitectureandTechnologySAPLibrary

    http://help.sap.de/saphelp_srm40/helpdata/en/8b/4fa9585db211d2b404006094b92d37/content.htm?frameset=/en/8b/4fa9585db211d2b404006094b92d37/frameset.htm&current_toc=/en/d6/4def8242df214aa27644e41da65d07/plain.ht 2/5

    WS14000075Withoutapproval,WS14000089OnestepapprovalWS14000145nstepapproval

    ApprovalworkflowsforpurchaseordersandchangeversionsofpurchaseordersTherelevantapprovalworkflowisstarted,dependingonvariousattributesoftheobjecttype PurchaseOrderEC(BUS2201) ,forexamplec hangeofaccountassignmentdata ,andt otalamountdifference .

    PurchaseOrderResponse(POR)WS14500001Automaticdatatransfer,WS14500019Manualdatatransfer

    WorkflowsfortransferofdataofpurchaseorderresponsetopurchaseorderDependingonthevariouscriteria,thePORdataiseithertransferredtothepurchaseorderautomaticallyormanuallybythepurchaser.

    Contract(CTR)WS14000086Withoutapproval,WS14000088OnestepapprovalWS14000148nstepapproval

    ApprovalworkflowsforcontractsandchangeversionsofcontractsTherelevantapprovalworkflowisstarted,dependingonvariousattributesoftheobjecttype PurchaseContract(BUS2000113) ,forexample changeofconditions .

    BidWS79000010Withoutapproval,WS79000002Onestepapproval

    ApprovalworkflowsforbidsTherelevantapprovalworkflowisstarted,dependingonwhetheramanageroranemployeeofthepurchasinggroupacceptsabidforabidinvitation.

    BidInvitationWS14500026Withoutapproval,WS14500027OnestepapprovalWS14500028nstepapproval

    ApprovalWorkflowsforbidinvitationsAfterbidinvitations(andtheirchangeversions)arepublished,oneofthesethreeapprovalworkflowsisstarted,dependingonthestartconditions.TheimplementationoftheBAdI BBP_WORKFLOW_APPROV_BADI isaprerequisitefornstepapproval(withback&forthprocessing).(Ifthisisnotthecase,themanagerofthepurchasingorganizationisdeterminedasapprover.)

    NewuserWS10000192

    Inthisworkflow,themanagerofthenewusercreatedhastoapprovethenewuser.

    NewpasswordWS10000223

    ThisworkflowstartsafteranEBPuserrequestsanewpassword.

    Newbidder/vendorWS10000209

    ThisworkflowstartswhenabidderorvendorrequestsanewuserfortheEBPsystem.

  • 27/5/2015 SRMBusinessWorkflowArchitectureandTechnologySAPLibrary

    http://help.sap.de/saphelp_srm40/helpdata/en/8b/4fa9585db211d2b404006094b92d37/content.htm?frameset=/en/8b/4fa9585db211d2b404006094b92d37/frameset.htm&current_toc=/en/d6/4def8242df214aa27644e41da65d07/plain.ht 3/5

    TransferofSCtoPMsystemWS10000202

    ThisworkflowcausesaSCtobetransportedasrequirementcoveragerequesttothePMbackend.(Onlyforclassicscenario!)

    TheseworkflowssupportfurtherSRMprocessesorareprovidedasanalternativetostandardworkflows:

    Workflowfor: Scenario

    SpendinglimitforSC(onestep)WS10000276

    Onestepapprovalworkflowforshoppingcart(alternativetoSCworkflows)Thesystemusesspendingandapprovallimitstofirstdeterminewhetherapprovalisnecessary,andthentodeterminetheapprover.

    SpendinglimitforSC(nstep,dynamic)WS14000109

    Multistepapprovalworkflowforshoppingcart(alternativetoonestepspendinglimitWFL)StepbystepapprovalofSCdependingonspendingandapprovallimit.

    SpendinglimitforSCwithBAdI(nstep,dynamic)WS14000133

    Nstepapprovalworkflowforshoppingcart(alternativetoallSCworkflows)DeterminationofapproveroccursdynamicallyviaaBAdI.

    ItemBasedApprovalforSCWS14500015

    MultistepapprovalofindividualSCitemsbyresponsibleapprover

    CompleteSCWS14000044

    CompletionofshoppingcartbypurchaserIncompleteshoppingcartcompletedbypurchaserbeforeapproval.

    PurchasingBudgetWorkflow(SC)(Workflowscenario)

    ApprovaloftheSCisnotdependentonitsvalue,butratherontheemployeespurchasingbudget

    VendorsfromOPIWS14000043WithoutapprovalWS14000030Onestepapproval

    ApprovalofvendorsRelevantapprovalworkflowisstarted,dependingonprocessorauthorization.

    LockingofSUSSuppliersWS145000021

    NotificationworkflowafteraSUSsupplierhasbeenlocked

  • 27/5/2015 SRMBusinessWorkflowArchitectureandTechnologySAPLibrary

    http://help.sap.de/saphelp_srm40/helpdata/en/8b/4fa9585db211d2b404006094b92d37/content.htm?frameset=/en/8b/4fa9585db211d2b404006094b92d37/frameset.htm&current_toc=/en/d6/4def8242df214aa27644e41da65d07/plain.ht 4/5

    WorkflowstartsafteraSUSsupplierhasbeenlockedAllpurchasersofthepurchasingorganizationOrganizationofthelockedsupplierreceiveanotificationviaemail.

    ProcurementcardWS10000093FirstapprovalWS10000100Secondapproval

    ApprovalofcardchargesThecardholderisresponsibleforapprovalunlessthesettlementvalueexceedsthespendinglimitsetinCustomizing.Ifthisisthecase,themanagerisresponsibleforapproval.(Formoreinformation,seetheIMG: SRMServer ProcurementCard ProcessProcurementCard )

    PurchaseOrderResponse(POR)WS14500007NotificationWS14500017Alertworkflow

    NotificationwhenaPORisreceivedandmonitoringofPORreceiptAsanalternativetotheworkflowformanualdatatransfer,( WS14500019 )thenotificationworkflowjustinformsthepurchaserthatthedocumentrequiresprocessing.ThealertworkflowmonitorsreceiptofaPORforaPOwherethe PurchaseOrderResponseExpected indicatorisset.

    StochasticDocumentCheck(IVandCF) FlexibleuseofapprovalworkflowsforstochasticdocumentcheckofinvoicesandconfirmationsDependingonthedocumenttype,itssubtype,andthedocumentvalue,youcancreateyourownrulesforusingcertainspecificworkflowsforrandomchecksofIVandCF.Formoreinformation,see:ReleaseNote ChangesinSAPBusinessWorkflow(EnterpriseBuyer4.0) ,Section WorkflowSettingsforStochasticDocumentCheck

    CorrectionofXMLInvoicesWS14500020

    CorrectionworkflowforerroneousXMLinvoicesErroneousXMLinvoicesarenolongerautomaticallysentback.Now,theycanbecorrectedorprocessedbytheresponsibleemployeebeforetheyareposted.Theworkitemcontainsalinkusedtobranchtoinvoiceprocessing.

    Aswellastheseadditionalworkflows,thereareotherworkflowsdesignedtomakeworkingwiththeSRMServereasier.Mostly,thesearenotificationworkflowsthatsendamessagetotheresponsibleprocessorwhenacertainsystemeventoccurs.Inaddition,youcaneasilychangetheapprovalprocessesofSRMdocumentsbyusing/activatingpredefineddefaultsettings.(Formoreinformation,seethe ChangestoSAPBusinessWorkflow ReleaseNote . )

  • 27/5/2015 SRMBusinessWorkflowArchitectureandTechnologySAPLibrary

    http://help.sap.de/saphelp_srm40/helpdata/en/8b/4fa9585db211d2b404006094b92d37/content.htm?frameset=/en/8b/4fa9585db211d2b404006094b92d37/frameset.htm&current_toc=/en/d6/4def8242df214aa27644e41da65d07/plain.ht 5/5

    ActivitiesYouconfigurethe SAPBusinessWorkflow settingsinCustomizing.MenupathintheImplementationGuide(IMG):SupplierRelationshipManagement SRMServer CrossApplicationBasicSettings SAPBusinessWorkflow

    COPYRIGHTBYSAPSEORANSAPAFFILIATECOMPANY. ALLRIGHTSRESERVED. PRINTEDFROMSAPHELPPORTAL. (ht tp: / /help.sap.com)