Skip to Content
author's profile photo Former Member
Former Member

Can we have two Shopping cart transaction type?

Hi SRM Gurus,

I am having a doubt.Please clarify

Is it possible to include two transaction types for shopping cart?The follow on documents corresponding to each one is different.

Transaction types of shopping cart can be the main criteria for determining approval process. In the Front end, how user can choose the transaction type, i.e whether in the User Interface screen, transaction type will appear for choosing? Or any customized program is required to include transaction types in the shopping cart screen.

Thanks in advance,

Ramkumar

Add a comment
10|10000 characters needed characters exceeded

Related questions

6 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Apr 10, 2007 at 10:05 AM

    Hi Ramkumar,

    Nice question

    I think up to SRM 5.0 it is not possible to create your own transaction type for shopping cart .

    But the thing is creation of Trasaction type cannot answer your question.

    The background for every transaction type has a Business Object and these Business Objects are linked to approval workflows and it is huge process.

    It is easy to customize the SRM system according to Product categories or with respective BADIs for defining your own business process.

    with regards,

    mahesh

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi

      Sounds interesting.You mean to say that you will be handling the Approval workflow with your logic and conditions.

      <b>Transaction type will not appear in front end user interface.</b>

      <u>Please read this -></u>

      Define Transaction Types
      In this IMG activity, you specify the transaction type of all the purchasing documents that are to be created in the Supplier Relationship Management (SRM) System. The transaction type controls the number range intervals from which the numbers of the documents are determined, as well as the status profile.
      
      Note
      The status profile documents the current business status of an object. This status controls the actions that can be executed with the object. For example, a bid invitation has the status held, which means it was temporarily stored without being checked. This status can be followed by the action change but not publish.
      If you work with both local purchase orders (POs) as well as POs in the backend system, specify as a transaction type for local POs the same identifier that you intend to use for PO document types in the backend system. For more information, see Define Number Ranges. In business terms, the document type and transaction type have the same function.
      
      When you have defined partner schemas, enter as partner schema ID the same abbreviation that you have defined in the IMG activity Define Partner Schema.
      
      In this IMG activity, you can also make the following settings:
      
      In the Bid Invitation transaction object type, you can specify default values for your transaction type. For example, you can specify that the Bidder Can Add Items field is activated when theContract Negotiation transaction type is created. You can override this setting in each individual contract.
      
      In contracts, you can assign the transaction types to one of two variants of the Contract transaction object type. These are purchasing contract or global outline agreement.
      
      In auctions, you can control which fields a bidder can view in the Live Auction Cockpit. For example, you can specify that the bidder is able to see the number of other bidders.
      
      In the Bid invitation, Contract, and Auction transaction object types, you can specify the transaction types of the follow-on documents.
      For example, you can specify for the Purchasing Contract transaction object type that the follow-on document is a bid invitation that has the transaction type request.
      
      Assign Event Schema
      By assigning an event schema to a transaction type, you activate the function SRM Alert Management, that is, alerts and/or messages can be sent for this transaction type. If no event schema is assigned here, then this function is deactivated.
      
      Choose the transaction object type and then open the folder transaction types. You can see the transaction types for the object type Select one of these via double-click. This takes you to the detail view. In the area General you will find the entry field Event Schema.
      
      Use the input help (F4) to select an available event schema.
      (The event schema must previously have been created for the corresponding object type using the IMG activity Define Event Schema.)
      
      Example:
      For the object type bid invitation (BUS2200) and the transaction type bid invitation (RFQ) (RFQU), you can assign the SRM-delivered event schema RFQ. This way you activate,for the documents of type bid invitation, all existing events which can then lead to alerts/messages. (The events for an object type must have been defined previously in the IMG activity Define Events.)
      
      Example
      In the backend system, you have created a purchasing document type - called EC1 for POs. You have assigned EC1 to your users in the BSA attribute (transaction type Follow-On Documents for Shopping Cart). You now want to create POs locally. To do this, you must create a transaction type - called EC2, for example. This is because:
      
      If a PO or purchase requisition is created in the backend system, the system automatically assigns it a document type (for example EC1).
      If a PO or purchase requisition is created in the SRM System , the system automatically assigns it a document type (for example EC2).
      Requirements
      
      Under number ranges you have created the number ranges for the local materials management documents.
      
      Further notes
      For SRM Alert Management see Release Note SRM Alert Management (new).

      Regards

      - Atul

  • author's profile photo Former Member
    Former Member
    Posted on Apr 10, 2007 at 10:44 AM

    Thanks Atul,

    Let me try from my end. If you find any answer, please let me know.

    Thanks & Regards,

    Ramkumar

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Apr 10, 2007 at 09:33 AM

    Hi

    Which SRM version are you using. ?

    See this link ->

    basic transaction type doubt

    Regards

    - Atul

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Atul,

      Thanks. Our's is SRM 5.0 .

      The doubt s with espect to Shopping cart transaction types, and not about PO transaction types. Whether can we have multiple transaction types for shopping cart? If yes, how can we have in the front end user interface?

      Thanks & Regards,

      Ramkumar

  • author's profile photo Former Member
    Former Member
    Posted on Apr 11, 2007 at 02:12 AM

    Hi Ramki,

    Assume that there are two PR document types, and based on which approval workflow (Release Strategy) is being triggered. In other words, workflow is not dependent on Organizational Units.

    This has to be mapped in SRM. Neither product category nor Acct assignment category is the classifying criteria. i.e same products can be procured for both document types.

    Thanks & Regards,

    Ramkumar

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi Ram

      I am not sure whether I understood correctly.

      1) Release strategy, doc type, classification are in R/3. We cannot use these in SRM.

      May be you are trying to use the same philosophy in SRM too.

      2) The conditions for SRM workflow are defined in SWB_PROCUREMENT. Ofcourse, Transaction type is one of them.

      Are you using this settings or are you using the workflow BADI ?

      3) If you are using SWB_PROCUREMENT, then I would suggest you to check all the parameters available there.

      3) If you are using workflow BADI, then I suggest the following:

      Create a custom field (check note 672960; it's easy) - ZPRDOCTYP with all values required for doc type. Use this field in your BADI for workflow.

      Best regards

      Ramki

  • Posted on Apr 30, 2007 at 03:23 PM

    Hello, I have written a page that tries to explain how the SC's document type determination process works in SRM .

    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/shoppingcartdocument+type&

    Regards, Luciano

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Chandrasekhar,

      If you chnage the function module in 'LBBP_SC_APPF03' from 'gc_no' to 'gc_yes', and selec the scond value you will still get the furst value coz still you are using the read statement index 1 to assign the value , that need to be changed also.

      Hi Luciano,

      Thanks for the useful link and info.

      Thanks and regards

      Iftekhar Alam

  • Posted on Jul 13, 2016 at 10:24 AM

    Hi,

    I have a similar requirement of creating three transaction types for Shopping cart. How did you do it ?

    Thanks

    Vaishali

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.