Transaction type in SRM

Hi all,
We are on SRM 7.0, ECC 6.0 (Classic Scenario).
I am not clear on how to maintain the transaction types in SRM and document type in ECC to create a PO successfully from a SC.My SC has been approved, but no PO is created in ECC.
I have copied doc type NB as ECPO in ECC. Pl let me know how to define a transaction type for this ECPO in SRM and with what number range.
Regards

Hi Sam,
Under Define number range for SC & follow on documents I have
                      From             To                 Current
01     0010000000     0019999999     10000089
PO     4500000000     4599999999     4500000009
RQ     6391000000     6391999999     0
I want to change the number range of PO as 460000000 - 469999999.(As I have created ECPO with a similar number range in ECC). But I am unable to delete (it says deletion only possible if status is initial). How do I resolve this?
In my org structure I have maintained ECPO.
What do I maintain under 'Define transaction types'?
Regards

Similar Messages

  • How to define an new New transaction type in SRM Environment?

    Hi All,
    There is a situation where in I have to add anew transaction type and link it to the existing process.
    If I am going to
    SPRO->SRM->SRM Server -> Cross appl.Basic Setting ->
    Define transaction type
    It gives me an un editable screen.
    My question is how to define a new transaction type here
    Kindly Let me know if there is any way to do it through ABAP .
    Thanks And Regards,
    Rupesh

    When you have gone through the path you describe you end up with a screen with a line for "define transaction types". To the left of the line are two icons - one to execute the function (the execute icon) and one with documentation (the text icon). Click on the documentation icon.
    Rob

  • No transaction types available in SRM

    Hi ,
    here i am using srm 7 . and created shoping cort and back po number  also genrated. but when i cross chek with back end po  is not there.
    i am running the background progrm clean_rfqrfq_up.
    i find out the following information :
    when assinging source of supply i find out  there is   No transaction types available in SRM  and cross cheak the config i maintained the   transaction types  in SRM
    i am thinking it is not carrying any transaction types so it is not creating po in back end. if it is so please let me know where i have to assing this ...
    this is in srm
    ECPO     Purchase Order     PO     02
    this is in bak end :
    ECPO     Standard PO - SRM     10     45     PO          SAP     NBF                             
    and maintend in user attribute this for document type also.
    and number ranges also correct,,,
    please let me know where i am missing the configaration.
    Thanks and Reagrds,
    S.Srinivasulu Reddy.

    Hi,
    Please check in SPRO -SRM whether you have maintained the config given below
    Define Objects in backend system
    Define backend system
    Regards
    G.Ganesh Kumar

  • Multiple PO document types/transaction types in Extended Classic scenario

    Hi All,
    We are on SRM_SERVER 550, Extended Classic Scenario.
    We have a requirement where we need to create multiple PO document types (based on certain criteria).
    I have noticed that in standard, there are only 2 transaction types provided for SRM PO - ECPO and ECDP.
    We need more document types and these should be triggerred automatically after SC is approved.
    I understand that we need to maintain all the PO transaction types in SRM, number ranges in SRM then maintain the same transaction types as PO document types in R/3 and same number ranges in R/3.
    I also understand that the change for document type needs to be done in BBP_DOC_CHANGE_BADI.
    I have 2 specific questions:
    1. We need to maintain attribute BSA for the users. Here we need to mention the document type and source system. What should be the source system mained in attribute BSA for ECS? Should it be the SRM system or R/3 system?
    2. In BBP_DOC_CHANGE_BADI to change the PO document type/transaction type in ECS scenario, which field should be changed? Should it be ET_ITEM- BE_DOC_TYPE?
    Regards,
    Srivatsan

    Srivatsan,
    To create new transaction type:
    Supplier Relationship Management --> SRM Server --> Cross-Application Basic Settings --> Define Transaction Types
    To create new number range:
    Supplier Relationship Management --> SRM Server --> Cross-Application Basic Settings --> Number Ranges --> SRM Server Number Ranges --> Define Number Range for Local Purchase Orders
    You can define to create automatic PO when a SC was created in: Supplier Relationship Management --> SRM Server --> Sourcing --> Define Sourcing for Product Categories
    Rgs,
    Pedro Marques

  • Document type and Transaction type

    Hi,
    Can someone give me a clear and detailed understanding of how to maintain transaction types in SRM system and document types in the backend system based on various scenarios (i.e standalone,classic. extended.....)
    Is it mandatory that the document type assigned in org plan attribute BSA be maintained in the local system as well??
    Thanks
    sunny

    Lol Sunny,
    Thanks for the compliment, but no, I'm in france. I work on SRM for now 5 years, so it helps
    In fact META BAPI are only BAPIs, with a certain way of developping: What SAP calls "Abstraction Layer".
    This allow you to manage Partner system version differences, and backend unavailability, the process is:
    ->META_BAPI
    -First try synchronously
    -->Read table BBP_FUNCTION_MAP (and now get into BADI) to get the exact function module to be called depending on the partner system type and its version
    --->Call of this function (which either makes local actions, or call the backend system with RFC)
    If the system was unable to call the partner system , it creates a job to re-try the call (based on what you entered in customizing).
    Here is the SAP description:
    <i>- Depending on the release level used, you can use various Business Application Programming Interfaces (BAPIs) to implement the business processes in the back end system. The abstraction layer encapsulates the BAPI calls in the back end system that are necessary to generate the back end documents from requirement coverage requests. The abstraction layer accesses the following sources of information:
    -Dispatcher: This function module analyzes the Customizing settings and then knows:
    --     Which driver it must call
    --     Which back end system it is communicating with
    --     The back end system release
    --     Driver: For each release level supported and each abstraction layer, there is a driver module that calls the BAPIs in the back end system.
    --     Spoolers: The spooler controls the transfer of documents from the Enterprise Buyer system to the back end system. If errors occur during the transfer, for example, the back end system cannot be contacted, the spooler is used as the queue for the requirement coverage requests. The spooler tries to contact the back end system at regular intervals and to transfer the documents.</i>
    Regards.
    Vadim.
    PS if you are really "amazed" please be more generous in your rewards

  • Transaction type for PR

    I have read that in PPOMA_BBP for doc type in R/3 we have to maintain for PR or if PO is created PO doc type.
    In our system PR is always created.So what is the doc type I should maintain. Should I maintain the doc type ZNB which is the PR doc type in backend. Is it possible to maintain ZNB in SRM.
    <b>Can anyone let me know how to maintain transaction type and number range if PR is getting created in SRM and backend</b>

    Hi jjj,
    You need to maintain the ZNB Transaction Type in SRM as a follow on document for Shopping cart and for Purchase Order .
    While creating PR in the backend system will consider ZNB as the follow on document.
    Maintain the Org attributes for R/3 document type in SRM.
    with regards,
    mahesh

  • Transaction types(PO types) not visible on SRM 7.0 portal

    Hi all,
    We added transaction types in the SRM 7.0system.But these are not reflecting in the SRM 7.0 portal.
    Under Purchasing role ->create Documents -> Purchase order .
    Once I click on the purchase order it is giving a table with columns PO type and PO desc.
    and showing a message the table does not contain any data.
    But SRM consultant added the transaction types(PO types) in the backe nd.
    Is there missing configuration steps?
    Thanks and regards,
    Rajesh

    Hello Rajesh,
    Few more pointers, if works:
    1. Check the roles, sometimes security restricts role by document types.
    2. Extended classic scenario is activated.
    3. As a standard, there are 3 purchasing tabs in SRM 7.0 for buyer depending on portal roles, ECC, SRM & harmonized role (ECC & SRM), Check if you are trying to create PO in SRM/Harmonized role purchasing tab & not in ECC. Easiest way to check is you will have shopping cart POWL visible in SRM purchasing tab.
    Hope this helps.
    Thanks
    Ashutosh

  • Pricing condition types in SRM 7.0

    Hi,
    We are using SRM 7.0, we have decided to go ahead with the pricing proceedure and the condition types which are there in ECC the same should be replicated to SRM.
    We have created the same pricing proceedure and the calculation scheema in SRM.
    Now my requirement is when i create a PO with the conditions and when i am transfering to ECC the PO should also be with the condition types. It should be a similar PO in ECC.
    Is this can be addressed.

    Hello All,
    As I have already mentioned the condition types in SRM are identically matched to ERP condition type hence the data is flowing correctly and even the idoc has the z-condition type Z123.The IDOC in backend ERP has status 53.
    On trial and error method we did unchecked the manual indicator check in the pricing schema for the relevant condition type and because of that now the Z-condiiton type can be seen in the backend ERP contract.
    If the indicator was checked, this means that this condition can be maintained only manually (directly in the transaction
    ME32K in ECC) and nothing can be transfer from other source.
    Note: If the same condition type is being used in more than one pricing procedure then ensure that the check bok is unchecked for agianst the relevant condition type.
    Thanks,
    Yatin

  • Error: "Transaction type could not be determined" during PO Creation fromSC

    Hi all,
    I'm working on SRM 5.5 with ECS.
    During the creation of  a PO  I want to add a SC as an item of PO.
    But when I chose the SC and click on the button Add to PO I recive the error:
    Transaction type could not be determined
    In the organizational unit I set the attribute BSA and DP_PROCT_TY.
    there are other steps I have to do to join the transaction type of SC and PO?
    rgs
    enzo

    Hi Enzo,
    First check if the attribute BSA and DP_PROC_TY have the same value.
    Then in the attribute value for BSA, change the source system for the document type to your SRM system.
    Create a new PO and a shopping cart.
    Try changing the PO by adding the shopping cart
    Hopefully your problem may get resolved.
    Thanks
    Sanjeev

  • WHAT IS THE CONNECTION TYPE FOR SRM

    HI
    WHAT IS THE CONNECTION TYPE IN SRM RFC DESTINATION.
    3-R3 ....ETC.

    Hi,
    depending on the application to connect to backend SRM system, your connection type may change.
    1. If you write Dynpro appliactions to use SRM System, at backend, it'll connect SRM via RFC.
    2. If you use ITS to create views of SRM Transactions, then the connection will be Dailog and URL
    note 730870 you should find the answer to your question
    Also check:
    http://help.sap.com/saphelp_nwmobile71/helpdata/en/22/042638488911d189490000e829fbbd/frameset.htm.
    Look for TCP/IP RFC destination in it
    <b>Reward points</b>
    Regards

  • Multiple transaction types

    Hi all,
    I am working on SRM 5.0 and ECC 6.0. Implementing extended classic scenario.
    1.] Can someone tell me how to create multiple transaction types for SC which result in PO's in SRM?E.g ACPO; EMPO etc
    2.]Further,when users create shopping cart, they should have the ability to select a transaction type before creating a shopping cart?
    Points will be awarded.
    Trey

    Hi to everybody,
    I am also interested in this topic.I created a new document type ZSHC for the shopping cart. Afterwards I assigned new number ranges to this document type.
    But I am not able to select the document type before creating a shopping cart.
    I wonder why this should not be standard, because I was able to do the above described settings in customizing.
    Any ideas?
    Best regards,
    Martina

  • Query on transaction type and BP monitor

    hi Friends
    what is the transaction type for sourcing and credit memo
    query on supplier and bp monitor. Are they one and the same. or Is supplier monitor is in Sus side and bp monitor is in EBP side.
    Regards
    Simha

    Hi,
    I dont think there is  transaction types for sourcing and credit memo
    Transation code for sourcing  is BBPSOCO01
    SPRO SRM--SRM Server -- sourcing ---Define sourcing for product categories
    Through the settings can definte SC undergo for sourcing.
    Purchasers can complete the SC,'s and create PO's In sourcing.
    SAP Enterprise Buyer evaluates Sourcing Customizing after a shopping cart has been approved, and makes a note in the shopping cart stating whether or not the shopping cart should undergo sourcing.
    Thanks
    prasad.s

  • Multiple values of attributes for Transaction type Bid in the Org Plan

    Hello All,
    I need to have Multiple transaction types for the Object Bid Invitation in the Org Plan.
    As the system is allowing only a single value,I tried maintaining the Table T77OMATTR by setting the attribute 'Tend_type' to take multiple values, but the whole attribute is set to not modifiable!
    I am not sure whether I am doing the right thing
    Can anybody advise on this please?
    Regards,
    Nagarajan

    Hi
    different transactions types, which can be selected in the transaction, are defined in SPRO via
    IMG/Supplier Relationship Management/SRM Server/Cross-Application Settings/Define Transaction Types. There you can create new ones as well activate/deactivate transaction types.
    The follow on document, PO or Contract, is defined per transaction type there as well.
    When you want to influence the transaction type used from Sourcing Cockpit when clicking on "Bid Invitation", this can be accomplished via BADI only in SRM 5.0. Check the BADI section - don't know it by heart.
    Cheers,
    Claudia

  • Local transaction types and Backend PO types

    We are using SRM 6.0 using Ext Classic. We are taking External requirements from R3 (purchase requisitions) and creating POs in SRM.
    Our problem is the following.
    We want to create four different document types of POs (ZPO, ZCS, ZIA, ZAD). The problem is that when we are creating the purchase order from the external reqt (through sourcing hub), we select the document type ZCS or ZIA or ZAD but SRM always creates ZPO locally and in R/3..
    Our question is: How can we create the PO according to the user's selection of transaction type and make sure that the correct PO type is created locally and in the backend. We have maintained all four transaction types in attribute BSA and also in R/3.
    Thanks!
    -Bakulesh

    Yes. DP_PROC_TY is meant for manual creation PO.
    and you can specify the doc types desired for the PO.
    Also please check that you have specified the internal no ranges for these doc types
    and they lie in the range of the external no range you will define in the back end PO no range interval
    and specify as external no range in ECC PO doc type.
    BR
    Dinesh

  • Get Material Type in SRM

    Hi Gurus,
    How to get the material type in SRM? If we enter the material in the product field in the shopping cart, based upon the material type some validation needs to be done in the shopping cart.
    Please advise if anybody is having any clue.
    Thanks & Regards,
    Aswini

    Hi,
    Now I got to know how to get the material type in SRM. Would like to share the information.
    Material along with the material type get replicated into SRM from R/3 system. In COMMPR01 transaction, we can search for the material by entering the number in the product id and then it will show the detail information. When the material is replicated into srm, it will be tagged to both the hierachies R3MATCLASS as well as R3PRODSTYPE. The category id corresponding to the hierachy R3PRODSTYPE will have the format MAT_XXXX where XXXX denotes the material type. e.g. MAT_ESRA where ESRA denotes the material type in R/3. The characters after MAT_  will vary.
    The below step is followed to get the material type in SRM:
    1. Get the product GUID of the material (product) used int he shopping cart from the BBP_PD transaction. Or the product GUID can be obtained from table COMM_PRODUCT.
    2. Get the Hierarchy GUID of R3PRODSTYPE from COMM_HIERACHY.
    3. Get the CATEGORY_ID from the table COMM_PRPRDCATR based upon product GUID and HIERARCHY GUID of R3PRODSTYPE.
    It will give the result in MAT_XXXX format. The remaining characters after MAT_ represents the material type.
    Hope this information will be useful.
    Regards,
    Aswini
    Edited by: Aswini Kumar Sahoo on Sep 18, 2009 5:29 PM
    Edited by: Aswini Kumar Sahoo on Sep 18, 2009 5:30 PM

Maybe you are looking for