Release strategy for Shopping Cart

HI SRM GURU
We are implementing SRM 4.0 and follow a classic scenarios.
While creating a shoping cart the approval of Shopping cart is based on various attributes like
Material Group + Cost Center + Value .
Can I change the standard workflow conditions and add new conditions like material Group and cost centers.
So that when I create a Shopping cart and change the cost center in the shopping cart, it goes to the head of the new cost center(for Approval) which is manually entered in the shopping cart.
Can this control be achived through the Org plan attributes.
Regards,
Nimish Sheth

Hi Yann
How do we change the parameteres and the starting Conditions say ,
follwoing is the situation -
Material group  Cost Center   Value   Release Person    
LGEN01           C019        5000       A1
LGEN01           C019        10000      A2
LCAT01           C019        5000       C1
LCAT02           C020        5000       C3
Like that we have 100's of combinations  bsed on cost center. Is is that I have to add all this in SAP Workflow start conditions .?????
regards,
Nimish Sheth

Similar Messages

  • Release strategy for GR?

    Hi,
    My company has requirement that GR should be subject to approval process before it can be posted. As far as I know there is no standard functionality in SAP for this (at least in ECC, as in SRM there is one).
    Has anyone encounter this before? And how you deal with this? I have tried to persuade the user to drop this, but the problem is they already have this functionality in their legacy (which is custom made web based application), so it is pretty hard to argue with them in this area.
    Any help will be appreciated.
    Best regard

    Hi Yosea,
    Yes you said is right that there is no Release strategy. And can't imagine the situation in the legacy as well for this approval process thru Release strategy while doing the GR. But there is another way of accepting the goods either partial or full using movement types, you can do so.
    My question is why do you (i.e., your client or company) want to control (through the approval process) at Goods receipt level. That makes complex and un logical as well, thats why there is an approval process comes into picture at PO (Purchase order is an external purchase document and is going out to an external party /vendor /supplier) against that they can supply the material /provide the services to the Organization/company and is required to control before issuing this perticular document called PO (i.e., work order and is required to be controlled thru Electronic release strategy in SAP) instead of manual before in legacy since there is money matter involved and needs to control over investment on Inventory /services purchases.
    But where as GR, this is an incoming document, what the meaning in controlling it through approval process. That is the way you have to conveincene the client or company.
    Ok fine. If still they want this functionality to be implemented (that is to controlling at the GR level for the goods coming in. Then there is another way to control it through receiving the stocks into different stock types using the respective movement types, but not through Release strategy such as Blocking (GR blocking), Quality stock (for checking the quanlity standards thru Quality Inspection) and then later you can move these stocks to Unrestricted use stock, so that this can be allowed to use further.
    I dont think there is a functionality in the SRM as well. As I know that you can receive the Goods in SRM through Online Desktop confirmation that too partial or full quantity, that is nothing accepting/approval for the Partial or full quantity that is received against the PO which is created wrto to respective Shopping cart. And that is how you can control the goods that are coming inside / received at Stores/WH inorder to maintain the good quality of Inventory.
    Note: Controll always suggested at the time of making agreement  (i.e., Release strategy for the PO) but not at the time of receiving the goods. Here while receiving the goods only thing that a Stores person can see tmainly is needs to check for the Quantity, Quality of the goods that are ordered, Delivery time, Mode of transport, Shipping instructions, etc. This will help them further in evaluating the vendor.
    Hence there is no logic is going for that option
    Hope it clarifies,
    Regards,
    Sapsrin

  • How to use customer extension table for schedule line for shopping cart ?

    Dear Experts,
    One of our client wants to have schedule lines in shopping cart item. I am thinking of using customer extension table at item level for shopping cart. Could you please help me on  how I should proceed with the appending the structures so that the end user can fill the shopping cart schedule line details?
    Which fields should I consider in such cases?
    Thanks and regards,
    Ranjan

    Hi.
    I guess you use SRM 7.0. Please go to IMG.
    SRM -> SRM Server -> Cross-Application Basic Settings -> Extensions and Field Control (Personalization) -> Create Table Extensions and Supply with Data
    Regards,
    Masa

  • One Step Workflow Activation for Shopping cart in SRM 7.0

    Dear Experts,
    On working to EXtended Classic Scenario, I need to configure one step approval for shopping cart in SRM 7.0.
    Currently it is providing me Auto Approval  by default and based on it PO is being created. I need one-level manager approval  shopping cart.
    I am working in Demo System of Extended Classic Scenario, I need only one step approval SC without any condition.
    Kindly tell me the configuration steps in SRM and please tell me one more thing is there  any need of  BADI or other coding for one-step approval?
    Thanks in Advance,
    Regards
    Pawan Keshwani
    Edited by: pawankeshwani on May 25, 2011 6:22 PM

    Hi Ashutosh,
    Thanks for quick reply.
    As per your comment when i am tring to activate /SAPSRM/C_SC_600_001_SP04  by t-code SCPR20, But It shows me a information pop up Maintain the client role and then Activation is Cancelled.
    Kindly tell me what i am missing or any other prerequisite step to do for this BC Set Activation.
    Thanks
    Pawan Keshwani

  • Release strategy for PO and Contract

    Hi,
    I maintain characteritic for PO
    Plant
    Doc Type
    Net Order Value
    Purchasing Group
    I maintain characteristic  for contract
    Company code
    Target Value
    Doc Type
    Purchasing group
    My class consist of
    Plant
    Doc Type
    Net Order Value
    Purchasing Group
    Company code
    Target value
    Q1: Do i need to maintain ALL characteristic value when i define my release strategy for PO or Contract as some characteristic only apply to PO only or contract only?
    Q2:  What option do i have if i need to maintain all characteristic value ? leave it blank ? empty
    Currently my PO release is working fine but when i try to maintain the contract release inside the class . my PO release is not triggering . I maintained diffrent release group for both PO and Contract .
    Thank for your advice

    First of all
    For purchasing like PO,pr,contract you can able to get in ekko table.No need to maintain separate release unless if it your business requirement.Take Document type as one of the characteristics it will distinguish whether it is PO or contract.
    You have to maintain all the characteristic value then only it will trigered release.
    Check the release indicator as well.
    Hope it will help.

  • Release strategy for quantity contract

    Hi Gurus,
    In quantity contract ..  target value will not filled by the value(in header details) as it is quantityt contract.
    We may have different line items with different cost..
    my doubt is how the release strategy will be triggered for the quanityt contract and how the system will consider the whole value of the contract..
    please explain/clarify
    regards
    subbu

    Hi,
    The release strategy for the contract will work in the exact mechanism as for the PO i.e. it will be determined  based upon the total net value of the entire purchasing document.
    Cheers,
    HT

  • Release Strategy for SA/Contract/PO

    Hi friends,
    Should we have different release groups and release codes in contracting/ SA/ PO.
    Because...
    I have maintained 4 characteristics in release strategy for PO _[ Comp Co, plant, porg, total net order value].
    But i want to maintan only 2 characteristics in release strategy for contract  [plant, total net order value]
    because the same is reflecting in contract config also.
    Is it possible..please help me frnds.
    Prabhu

    Hi Prabhu,
    Unfortunately you need to maintain characteristics of all possible values for company code and plant for contractsu2019 to subject the release.
    Wish that SAP would be more flexible with release of PO, Contract and RFQ but it does not.
    Regards

  • Release Strategy for Contract is not getting picked whereas it is ok for PO

    Dear Experts,
    I have created release strategy for PO with doc type, p.org, net value as chars and frg_ekko as class and release group as 02.
    I kept NB,FO,MK and WK as char values. it is working fine for PO's whereas it is not getting picked for Contracts. we need same release strategy for PO as well as for Contract.
    Kindly resolve the issue.
    Satish

    S0004830404 wrote:
    Dear Experts,
    >
    > I have created release strategy for PO with doc type, p.org, net value as chars and frg_ekko as class and release group as 02.
    > I kept NB,FO,MK and WK as char values. it is working fine for PO's whereas it is not getting picked for Contracts. we need same release strategy for PO as well as for Contract.
    >
    > Kindly resolve the issue.
    >
    > Satish
    hi,
    use create other characteristic for value CEKKO-GNETW in this use the mk , wk values in value field and assign this characteristic to your class and save.
    Thanking you

  • Release strategy for Schedule lines in SD

    Hello All
    Can we create a release strategy for Schedule Lines in Scheduling Agreement? If Yes How?
    I have already maintained a release strategy for Item Level... which I want to put it for Schedule line as well....
    Thanks in advance.

    Hello,
    I think you are in the wrong forum. Please choose the right forum category and post it there.
    Matthias

  • Release strategy for Scheduling Agreement(SA)

    Dear Forum,
    This issue is with regards to the release strategy for Scheduling Agreement(SA)
    Until now release has only been applicable to contracts at our client site. But we now plan to introduce it for SA as well. Such a feature is available in SAP but the problem is that with the given release strategy GR is not allowed until the release is affected. The system allows you to post the delivery schedule.
    Now what I want is that after making the SA the system should not allow to make delivery schedule if release is not affected.
    We also have MRP run at client site..Kindly suggest the procedure as, how to configure it.Are der any User Exit for the same,if so please discuss..
    Warm Regards
    Nainesh
    SAP ECC 6.0

    Hi,
    What's the SA Type that was created via MRP.
    If it's LP (without release document), release will not do anything BUT
    If it's LPA (release document), then you will not be able to Post the GR until release is affected.
    Thanks.
    Scheduling Agreement can be categories as
    1) LP (without release document) and
    2) LPA (with release document)
    If use LP, you can do GR without release but with LPA, you need to release the schedule line via ME38.
    Thanks.
    NanoSAP  
    Posts: 58
    Registered: 1/5/09
    Forum Points: 6 
       Re: release strategy for Scheduling Agreement(SA)  
    Posted: Jun 26, 2009 8:32 AM    in response to: sathish.kumar           Reply 
    Dear Mr.Satish,
    Thanks a lot for your earliest reply...But my point is i want the system should not allow to make delivery schedule if release is not affected...Though schedule lines are generating through MRP run...Is is possible,by any chance...??

  • How to setup a release strategy for store generated purchase order

    Hi there,
    Does anybody know how to setup a release strategy for store/plant generated purchase order? I have a request from our client, but I never cross this before. Please help and let me know the step with every single detail.
    Greatly thank for your help.
    Kind Regards,
    2tea

    Please go thru the below Release Procedure and check whether you have maintained all the settings properly.
    PO RELEASE STRATEGY
    The release code is a two-character ID allowing a person to release (clear, or approve) a requisition or an external purchasing document. The release codes is basically controlled via a system of authorizations (authorization object M_EINK_FRG).
    Use SE12, structure CEKKO to check all the fields available for controlling the Purchase Order.
    e.g. If the total value for the Purchase Order exceeds 10,000, release strategy 01 is assigned to the Purchase Order. There is only one characteristic created in this example. For controlling the Purchase Order type, create characteristic for CEKKO-BSTYP and the value NB.
    CT04 - Create Characteristic e.g. NETVALUE
    Click Additional data Table name CEKKO Field name GNETW and press enter
    (for currency dependent field, you are prompt to enter the currency which the system then converts the currency of the Purchasing document into this currency)
    In the Basic data (X refers to tick),
    X Mutliple values
    X Interval values
    In the Value data, in the Char. value column, type >10000 and press enter
    Save your data
    CL02 - Class
    Class - Create REL_PUR
    Class type - 032
    Click Create
    Description - Release Procedure for Purchase Order
    In the Same Classification section, click Check with error
    In the Char. (characteristic) tab, type NETVALUE to assign your characteristics to the class
    OMGS - Define Release Procedure for Purchase Order Type
    Release Group - New entries
    Rel.group Rel. Object Class Description
    02 REL_PUR Rel. Strategy for PO
    Release codes - New entries
    Grp Code
    02 01
    Release indicators
    Release indicators Release Description
    0 Blocked
    1 X Release
    Release Strategy
    Release group 02
    Rel.strategy 01
    Release codes 01
    Release status 01
    Classification Choose your check values
    OMGSCK - Check Release Strategies
    (make sure there are no error messages)
    Once the Purchase Order is not release, buyers will not be able to print the Purchase Order.
    Goods Receipts will be shown with Message no. ME 390 - Purchasing document XXXXXXX not yet released.
    In 4.6c, Purchase Order with Release Strategy have a tabs at the end of the Header. This allowed the buyers to check the release status of the Purchase Order.
    The person with the release authorization have to use ME28 to release the Purchase Order.
    Regards,
    Ashok

  • Workflow for shopping cart

    Hi experts
    I am in SRM 7.0 and triing to use Process controled workflow, I have done some configurations for shopping cart aproval but no workflow is started and in shopping cart appear as in aproval.
    What cold be missing?
    Thanks
    Nilson

    Hi Guys
    Urgent
    In Sourcing cockpit field having morethan 1000 line item Shopping cart.  Could anyone help me to get the sourcing cockpit shopping cart entire report in a single report.
    We use to download the report morethan on hour on a daily basis.If anyone help me out for this really appriciated.

  • Process Controlled WF for Shopping Cart

    Hi,
    We have implemented process controlled workflow for shopping cart approval.
    1. Created a bespoke schema for the approval process
    2. Defined 5 process levels in the schema
    3. changed the BRF event at the schema evaluation level. It now
    contains a constant with the name of new schema create in step 1.
    4. Decision set used is item based approval for partial documents (Type 4)
    4. The first process level is get the technical approval from bespoke
    table based on material group. For that we have first created a
    Responsibility Resolver Name - ZTECHNICAL_APPROVER.
    We have implemented the BADI - /SAPSRM/BD_WF_RESP_RESOLVER. Assigned
    the filter as BUS2121 and ZTECHNICAL_APPROVER.
    5. Now we have placed the external debugger in BADi. when we create
    the shopping cart the flow doesn't stop at the break point. The item
    reaches to the last step of Automatic approval (Rejected).
    6. We think that schema is getting evaluated, however the process
    level is not getting called.
    7. Before we created schema, all the carts wer getting "Approved" by
    automatic step. In our schema the automatic step is "Rejected", hence
    the carts are getting rejected.
    Could you please let me know what could be reason for BADI
    implementation not being called or is there any config step which we
    are missing?

    Hi,
      I think your process level evaluation id is not true, that is the reason system skips the process level.. Can you check your evaluation event-expression code. What do you see in SLG1?  For testing purpose change the evaluation id to 0EV000 and check. Make Sure you debug through the user(requester) that you are creating the SC. Please test and let me know...
    Saravanan

  • Wrong approver for shopping cart

    Hi Friends,
    I've found something very strange in my SRM system for Shopping cart approveal process.
    One of my SC is waiting for approaval by a approver who is assigned to different plant  and he has got nothing to do with this SC.
    The SC's basic data contains the responsibility  of some other LPR group for which approver is different and he is the actual approver of this SC.
    Can you guys provide some link where i can find documents related to approval process in detail and also the organisation structure material as i am new to SRM..? after providing the solution for above querry...
    Thanks in advance
    ss

    Hi Volkoale,
                    I am also facing the same issue. If you have resolved it kindly post your approach as it will be helpful to the community.
    In my case, there is one  cutomized table that contains list of approvers, but I am yet to debug and find the source of data for this table. Your reply will be rewarded.
    Cheers,
    Kris

  • New document type for shopping cart /PO

    Hi Gurus,
    I have created a new transaction type ZSHC for Shopping carts in SRM. I have given it a new  number range.
    while creating a shopping cart , how do i ensure that my shopping carts get created with this transaction type?
    is there any attribute which controls this ?
    Regards,
    Mangesh

    Thanks Shrini for your response.
    BADI "BBP_CREATE_BE_PO_NEW" does not exist in SRM 4.0. The corresponds BADI in SRM 4.0 is "BBP_CREATE_PO_BACK".
    The documentation of this BADI says that it can be used to change all data TRANSFERRED TO THE BACKEND SYSTEM to create a purchase order.
    I would want the document type to be selected when the PO is created in SRM and not when SRM transfers the PO to the backend. Because in that case I fear that SRM can have one doucment type and R/3 would end up having different document type for same PO.
    I will activate the BADI and keep the thread posted.
    Thanks
    Venkatesh

Maybe you are looking for