Creator Name Purchase Requisition

Hi experts
one i've created a ShC the Purchase Requisition was born on Back-End system.
Into PR's item detail, in the folder Contact Person there is the field "Created by". I'd like to how if there is a way to change the system user "SRMREMOTE" with the name of real Shopping Cart creator.
Regards
andrea

Hi Andrea,
please see the notes:
990767
988490
Regards,
Peter

Similar Messages

  • Purchase Requisition - Validate Cost Center

    Hi,
    I need to check the data when creating a Purchase Requisition with reference to an existing Purchase Requisition. Currently, I am using the user exit EXIT_SAPLMEREQ_005 to carry out these checks.
    One of the checks that I need to do is to validate Cost Center. However, in this user exit, there is no cost center found in any of the imported parameters. Hence, I tried to use the function module 'COBL_RECEIVE'. However, the Cost Center retrieved is not refreshed and is incorrect. Are there any other ways where I can retrieve the correct Cost Center that is populated from the reference Purchase Requisition?
    Will appreciate any help in resolving this issue.
    Thanks lots.
    Cheers,
    Liyan

    Hi
    use the BADI in SE18 Tcode
    ME_REQ_POSTED
    implement this and use
    the Method POSTED has the parameter IM_EBKN which has KOSTL field
    this will work
    see the sample code for this BADI
    BAdI Name: ZPUR_RFQ (Implementation name) Purchase Requisitions
    Definition Name: ME_REQ_POSTED
    Interface Name : IF_EX_ME_REQ_POSTED
    Implementing Class: ZCL_IM_PUR_REQ
    Method :            POSTED
    METHOD if_ex_me_req_posted~posted .
      TYPE-POOLS: pgrt.
      DATA: t_txpdat TYPE STANDARD TABLE OF txpdat.
      DATA: s_txpdat TYPE txpdat.
      DATA: t_ident  TYPE pgrt_t_obj_ident.
      DATA: s_ident  TYPE pgrt_obj_ident.
      DATA: ident_tmp TYPE eketkey.
      DATA: nmrid_init TYPE txpdat-nmrid.
      DATA t_obj_event TYPE pgrt_t_obj_event.
      DATA s_obj_event TYPE pgrt_obj_event.
      DATA t_event     TYPE pgrt_t_event.
      DATA s_event     TYPE pgrt_event.
      DATA change_yes  TYPE c.
        IF l_s_eban-estkz NE 'B'.
          CLEAR v_mtart.
          SELECT SINGLE  mtart INTO v_mtart FROM mara WHERE matnr = l_s_eban-matnr.
          IF v_mtart EQ 'ZERS' OR v_mtart EQ 'FHMI' OR v_mtart EQ 'UNBW'.
            MESSAGE e000(zm_msg) WITH 'You are not allowed' 'to create PR for stock items'.
          ENDIF.
        ENDIF.
        IF  l_s_eban-knttp NE 'F' OR l_s_eban-pstyp NE '9'.
          IF l_s_eban-knttp NE 'A'.
            IF ( l_s_eban-pstyp NE '9' AND l_s_eban-pstyp NE 'D' )  AND l_s_eban-matnr EQ space.
              MESSAGE e000(zm_msg) WITH 'You cannot create' 'a PR without material number'.
            ENDIF.
          ENDIF.
        ENDIF.
      ENDLOOP.
    ENDMETHOD.
    reward points if useful
    regards
    Anji

  • Purchase requisition and cost center authorization check

    Hi all,
    in a R/3 4.7, I need to check the cost center (or profit center) when managing (create/modify/view) purchase requisitions.
    I have not found any auths object which perform this check.
    Any idea ?
    A BADI seems to be he only solution, inserting an authorizaton check.
    Thanks
    Andrea

    Hi
    use the BADI in SE18 Tcode
    ME_REQ_POSTED
    implement this and use
    the Method POSTED has the parameter IM_EBKN which has KOSTL field
    this will work
    see the sample code for this BADI
    BAdI Name: ZPUR_RFQ (Implementation name) Purchase Requisitions
    Definition Name: ME_REQ_POSTED
    Interface Name : IF_EX_ME_REQ_POSTED
    Implementing Class: ZCL_IM_PUR_REQ
    Method :            POSTED
    METHOD if_ex_me_req_posted~posted .
      TYPE-POOLS: pgrt.
      DATA: t_txpdat TYPE STANDARD TABLE OF txpdat.
      DATA: s_txpdat TYPE txpdat.
      DATA: t_ident  TYPE pgrt_t_obj_ident.
      DATA: s_ident  TYPE pgrt_obj_ident.
      DATA: ident_tmp TYPE eketkey.
      DATA: nmrid_init TYPE txpdat-nmrid.
      DATA t_obj_event TYPE pgrt_t_obj_event.
      DATA s_obj_event TYPE pgrt_obj_event.
      DATA t_event     TYPE pgrt_t_event.
      DATA s_event     TYPE pgrt_event.
      DATA change_yes  TYPE c.
        IF l_s_eban-estkz NE 'B'.
          CLEAR v_mtart.
          SELECT SINGLE  mtart INTO v_mtart FROM mara WHERE matnr = l_s_eban-matnr.
          IF v_mtart EQ 'ZERS' OR v_mtart EQ 'FHMI' OR v_mtart EQ 'UNBW'.
            MESSAGE e000(zm_msg) WITH 'You are not allowed' 'to create PR for stock items'.
          ENDIF.
        ENDIF.
        IF  l_s_eban-knttp NE 'F' OR l_s_eban-pstyp NE '9'.
          IF l_s_eban-knttp NE 'A'.
            IF ( l_s_eban-pstyp NE '9' AND l_s_eban-pstyp NE 'D' )  AND l_s_eban-matnr EQ space.
              MESSAGE e000(zm_msg) WITH 'You cannot create' 'a PR without material number'.
            ENDIF.
          ENDIF.
        ENDIF.
      ENDLOOP.
    ENDMETHOD.
    reward points if useful
    regards
    Anji

  • Purchase requisition creator

    Hello all, I am working in SRM 7.0 and I need to know who is the user that appears as creator in the purchase requisition that SRM sent to MM backend system. Who appears in the created by tab in the purchase requisition?
    I can´t test in my system because we have problems and I need to check it urgently
    Thanks
    Rosa Rodríguez

    Hi ,
    Created by will be the user with which the job clean_reqreq_up is scheduled.
    Thanks
    Iftekhar Alam

  • Purchase requisition approved date field name by differnt release codes

    can any body give me field name of the date of purchase requisition released by the release code.
    regards
    reddy
    Edited by: Ian Wong on Sep 18, 2008 6:37 PM

    Hi,
    Table name is EBAN
    Field name is BADAT.
    Pass Pur Req no..you can get the Date.
    Rgs,
    Dhanush.

  • Table name for Open purchase requisition / Purchase Order Number's

    Hi,
    I want to delete some Asset Number's. When i m deleting those, system give a error message You cannot delete. Open purchase requisition exists..
    From where i can found those Purchase Requisition / Purchase Order Number's. Is there any table, where i can found these numbers.
    Regards..

    hi,
    In the SAP Order Transactions ME21N, ME22N and ME23N, you can select by purchase requisitions in the document overview (selection variant -purchase requisitions).If you do so, it is possible to select explicitly by open and released purchase requisitions...
    OR
    In Transaction MEPO, in the document overview you can select by purchase requisitions. Here you can select only open purchase requisitions and execute...
    Regards
    Priyanka.P

  • Table Name of Purchase Requisition Grid Line Item (SAP-AFS)

    Dear All,
    As im in the midst of preparing a report on the purchase requisitions with grid value and its respective quantity for those which are not converted as POs.
    im not able to find the table which holds the AFS grid details related to the PR. im using EBAN to fetch the PR header and line item details and i tried joining with the EKET table, but resulting with the list of PR details those which are converted as POs, since EKET holds the PO sheduled line item details.
    Reference Transaction - me53n - Item details table control.
    Kindly help me to find the table which hold the above said data.
    thanks in advance.Rating assured.
    Message was edited by: Raja K.P

    Hi Raja
       The tables you have mentioned are enough for extracting the details you need. Hope the below code helps you.
    tables: eban, eket.
    parameters: p_werks like eban-werks.
    select-options: s_bsart for eban-bsart,
                    s_erdat for eban-erdat obligatory,
                    s_matnr for eban-matnr.
    data: begin of itab occurs 0,
             banfn like eban-banfn,
             bnfpo like eban-bnfpo,
             bsart like eban-bsart,
             matnr like eban-matnr,
             menge like eban-menge,
             ebeln like eban-ebeln,
             ebelp like eban-ebelp,
             menge1 like eket-menge1,
           end of itab.
    start-of-selection.
      select a~banfn a~bnfpo a~bsart a~matnr
             a~menge a~ebeln a~ebelp b~menge
             into table itab
             from eban as a
             inner join eket as b
             on b~ebeln = a~ebeln
             and b~ebelp = a~ebelp
             where a~werks = p_werks
             and   a~bsart in s_bsart
             and   a~erdat in s_erdat
             and   a~matnr in s_matnr
             and   ( a~ebeln eq space  or
                     a~menge ne b~menge ).
    Now internal table itab will have all the open PR Numbers, for partially open PR's you will have itab-ebeln populated. For these entries subtract itab-menge1 from itab-menge to get the open qty.
    Kind Regards
    Eswar

  • Can't use Overall Release for Purchase Requisitions

    I have two groups, AA and ZZ.  Each group has it's own Class.
    Group AA uses Cost Center Class (CN)  (uses Characteristics Cost Center and Line Amount)
    Group ZZ uses Order Class (OC) (uses Characteristic Order)
    I have built one and only one Release Strategy for each of these Groups.  These Strategies both work successfully when I select the other group to be the group for Overall Release.  That is, if I set ZZ to be for Overall Release, then create a requisition, the release strategy for Group AA is applied successfully.  However, if I modify the req the strategy for ZZ, does not get applied.
    The opposite is true.  When AA is set to be for Overall release, then ZZ works.  However, if I modify the req, then AA's release strategy does not get applied.
    Again, both strategies work correctly when the other Group is set to be the one to use for Overall Release.  However, neither strategy works if its group is set to be the one for Overall Release.
    What am I missing?  I only have two classes, two groups, and two release strategies.

    SAP Standard system allows only 8 levels of release codes.If client requirement is more than 8 then for excess release codes customisation is done by the technical team (Abapers).Lets take an example of 15 release levels required for a client according to his Business needs then in this case initial 7 codes are customised and remaining 8 release codes are configured in the system.
    Release procedure is of two types
    Release Procedure without classification
                 This procedure is applicable only for Purchase Requisitions.
                 Here PR is released Item by Item only.
    Release Procedure with classification
                This procedure is applicable to PR,RFQ,Service Entry sheet,RFQ,PO,Contract  and scheduling agreements.
                Item by Item and Header level releases can be configured
                For PR - both item by item and Header level release can be configured
                For external purchasing documents - Release is possible only at Header level.
    Step 1:
    Create Characteristics
    In this step we need to create characteristics - conditions to be satisfied for triggering Release startegy.For example client has asked to set release strategy based on 3 inputs.Combination of value, Plant and Purchasing group
                1) Total value of PR more than Rs 50,000
                   create  characteristic as "Release_PR_total_value" in transaction code CT04.
                  Tab -  Basic data " Data type --- CURR currency format", "Decimal places - eg. 2 " and "currency  eg. INR or USD"
                  Tab -values key in > 50000 INR
                  Tab -  Additional Data-  Table Name "CEBAN" and Field Name "GSWRT"
                  Tab - Restrictions - class type - 032 - Release strategy
                2) Plant
                     Create characteristic "Release_PR_plant" in transaction code CT04.
                     Tab - Basic data - Data type - CHAR; Number of chars - 4
                     Tab - Values - Key in all the plants for which you are required to configure release proc.  eg. 1000,2000,3000
                     Tab - Additional data - Table name CEBAN and Field Name is WERKS.
                3) Purchaisng Group
                     Create characteristic "Release_PR_PurchasingGroup" in TCode CT04
                    Tab - Basic data - Data Type - char, Number of chars eg. 3
                    Tab - values - Key in all the purchasing Groups for which Release proc. is to be configured as required by Client.
                    Tab - Addnl Data - Table Name CEKKO and field name - EKGRP
    Step 2:
    Define class in transaction code CL02
    Menu path SPRO>Materials Mgmt>Purchasing>Purchase Requisition>Release Procedure>Procedure with Classification>Edit classes
    Here we assign all the above created Characteristics to a CLASS so that a release strategy to be triggered when all the conditions are met.
    Create a new class with free choice of names as "PR_Release_proc" in transaction code CL02.*Key in the class name and select class type as 032 - RELEASE STRATEGY then click on symbol create to enter all the details as mentioned below.
    Tab - Basic data - Enter description as "PR_Release-Proc",
    status- Released, Same classification - check the push button - Warning Message
    Tab- CHAR Enter above created 3 characteristics
    1.Release_PR_total_value
    2.Release_PR_plant
    3.Release_PR_PurchasingGroup
    step3:   
    Menu path is
    SPRO>Materials Mgmt>Purchasing>Purchase Requisition>Release Procedure>Procedure with Classification>set up procedure with classification>
    here define
    1.Release Groups
    Release group 01 is used for Purchase requisitions and 02 for Purchase orders.
    Here assign class "PR_Release_proc" against release code "01"
    check "OvRelPReq" indicator for over all release (All line items )of document in one shot else it will be released line item wise.
    2.Release codes
    Release codes are assigned to Release groups, in Workflow these release codes are tagged to users' SAP IDs through which they will be able to approve or reject a PR in SBWP(Inbox in SAP Business workplace.
    PRs are released by users in transaction code ME54N.
    Eg
    Type of user            - Level -             Release code                    
    PR creator - clerk or Business user -  
    Approver    -  Supervisor                 -   R1
    Approver  -   Project Lead              -   R2
    Approver   -  Asst. Manager             -  R3
    Approver   -  HOD/General Manager  - R4
    Release codes R1 to R5 are assigned to corresponding users.Manager R4 can only approve the PR if prior approvals till R3 are completed else not in ideal situation.
    For detailed info please refer
    http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
    3. Release Indicator:
    Release indicators show the release status of a Purchase Requisition.
    For detailed info please refer SAP Help official site
    http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
    4.Release Pre requisites:
    These define the order in which individuals or departments release the PR in sequence.
    3.Release strategies
    Create a new release startegy  eg ."A1" or "U1" , write its description PR release for value >1 lakh
    Now select release codes according to the Chart of Authority set by your client.
    Eg.
    Release startegy " A1 - PR release for value >1 lakh"
    R1 - Supervisor   
    R2- Project Lead    
    R3- Asst. Manager 
    R4- General Manager
    Now click on" Release  Prerequisites "push button and check all the boxes in ascending order.Save the document
    click on "Release statuses" push button, check release statuses then click on "Continue" push button.
    In third push button you can maintain CLASSIFICATION data or later you can directly mainatain in transaction code CL20N for this strategy.
    Classification data for example
    1. Value - > 100000
    2. Plant - 1000,2000,3000 etc
    3. Purchasing groups - 101,102,103 etc
    By clicking on "Release Simulation" push button you can check whether release is getting affected for configured release codes or not.
    In this way you can configure all the required Release startegies.
    Now create a PR in T code ME51N with the above conditions then a new tab will appear in PR creation screen at the time of check.Save the document and this can be released by respective users in TCode ME54N.
    Tcode - ME54N - For Individual Release
    Tcode - ME55 - For Collective Release
    For detailed info please visit SAP HELP website
    http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
    http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
    Regards,
    Indranil

  • Creator Name Missing

    Dear Friends
    I attach document to a Purchase requisition by Assign and store method in SAP Archive link.
    The document is linked to PR properly through GOS>Attachment List.
    But I am not able to see the creators name in hit list when I see list of document linked through services for object.
    Can you please guide me if I have missed any configuration.
    With Regards
    Mangesh Pande

    Thnaks Friends

  • Release strategy for purchase requisition does not kick in

    Hi Gurus!
    I've been struggling with this issue for some weeks now.
    I have set up the release strategy configuration for purchase requisitions with classifications.
    However, if I create a purchase requisition the release functionality is not taken into account by the system.
    See below some more information regarding my configuration:
    1. I've created a new characteristic "REL_PR_GROUP". Status: released, Multiple values, Number of Chars 3, 7 values (TR1, TR2, TR3....TR7), Table name: CEBAN, Field name: EKGRP, Procedure for value assignment set to not ready for input.
    2. I've created a new class: "REL_PR_ANPC". Class type 032, Status: released, Same classification: do not check, Char: "REL_PR_GROUP"
    3. I have one release group "T1", Rel. object 1, OverReqRel is marked, Class: "REL_PR_ANPC"
    4. I have 5 release codes. Grp: T1, Code: 01....05
    5. I have 2 release indicators:
    "R = Released", Rel. for ordering is marked, Changeabil: 4, Value chgs. 100,0
    "X = Blocked",  Changeabil: 4, Value chgs. 100,0
    6. I have 1 release strategy:
    "T1 with Grp T1"
    - one release group, 01 Manager
    - release prerequisites not applicable because of only one release group
    - release status, nothing marked = blocked, 01 marked = released
    - classification, purchasing group is TR1 or TR2 or TR3 or TR4 or TR5 or TR6 or TR7
    I intentionally kept the configuration as simple as possible so I can try to get it working first.
    Now if I create a purchase requisition for an item with release group T1, I would expect the release strategy to be activated. However, this is not the case. I don't see the "release status" tab in the PR, and if I try to relase via ME54 the system says the PR is not relevant for release.
    Could you please assist in getting this working?

    Hi,
    Have you checked in CL30/CL30N if your release strategy is derived successfully?
    See section 3 of Note 365604. A small section of it:
    You can use transaction CL30 search for an object using the data
    of the purchase requisition/purchase order. Here, it is important
    that the object search determines exactly one strategy. If this
    is not the case, this indicates that there are overlapping
    strategies in the system or that the release strategies in
    Customizing do not correspond with those from transaction CL24.
    See the previous point. If the object search returns more than
    one result, the system subsequently determines an incorrect
    release strategy or no release strategy at all.
    If it is derived successfully, next, check the user exit EXIT_SAPLEBND_001 as per Note 371667:
    The following assignment statement has to exist within activated SAP
    enhancements M06B0002 (include zxm06u13) and M06B0005 (include zxm06u31)
    for purchase requisitions:
         E_CEBAN = I_CEBAN.
    Regards,
    Purnima.

  • How to find out userid of purchase requisition at each item level

    for a particular requisition at each item is released by a some user, how to find out these user name.
    ex.
    pur.requi     pur req item    ueser_id
    10092188    00001            ?
    10092188    00002            ?
    10092188    00003            ?
    10092188    00004            ?
    in the above data purchase requisition is same but purchase
    requisition items are different. in this i want to find out user
    id of releaser for each item of particul purchase requisition.

    dear friend
    in table
    there is group
    tabkle : eben
    field:    FRGGR
    you get it easily.
    rewards are expecting:
    vivek

  • Purchase Requisitions Approval Error

    Hi,
    We are working in Oracle Applications 11i. We have the follwoing modules installed and used: Purchasing, Inventory, HRMS(Payrol), General Ledger, Assets, Payables.
    I am trying to fill in the gaps in our initial setup in order to enable the user to use Purchase Requistions documents.
    Purchasing Super User wishes to create a Purchase requistion herself and get it approved and then distribute the approved requistions amongst the buyers. Is this possible??? How can we implement this? Can we assign the superuser to aan approval hierarchy of one level?
    Also, I have created a multi-level position approval hierarchy , run Fill Employee Hierarchy, and assigned it to the Purchase Requisition document.
    Me, in the 1st level have created a Purchase Requistion,I submitted for approval and then had the error:
    APP-PO-14142: In Exception of Start_Wf_Process()-PO_REQAPPROVAL_INIT1.Start_WF_Process: In Exception handler: ORA-20002: 3108: Root Process could not be determined for item XXXXX. There may be a problem with item type selector function, or you may be required to supply a starting process Name.
    Can someone advise please....
    Thank you...

    Hi again,
    Now please help me in the first part of my post.
    How can I setup Purchasing Requisition in one-level hierarchy and approval?
    After the Reuisition is approved, in order to control the load balance , how can the super user distribute it to buyers to follow up the standard purchase order and submit it for approval?
    Thank you

  • Workflow error in release Purchase requisition

    Hi All,
    I configured the settings for workflow in Purchase Requisition.(both purchsing & task specific )
    Now, my workflow is started but its status is Error.
    actually it is not able to find the recepient in role 20000026.As i already mark relevent release code as 1 & also assign US user id in the PR release settings & also put the User ID in task specific customization.
    Still i am facing this error.One thing i want to mention is i am not aware of the settings required in the Edit Qrganizational Plan tab in SPRO.
    If some more clarification is required ,i will prode the same..
    Plz suggest some solution in this regard with T codes & bit detail.
    Thanks & Regards,
    Sandeep Sharma

    Sandeep,
    Okay here's some details which will help you out. I presume that you have done customizing for PR release strategy.
    If not then follow this procedure:
    http://help.sap.com/saphelp_47x200/helpdata/en/04/92761846f311d189470000e829fbbd/frameset.htm
    Once you establish release strategy , event releasestepcreated will automatically created by system based on release codes.
    so say for a standard pr type you have defined two release codes I1 and I2 (based on certain amount- you can see this in class characterisitic using tcode CL02) and class type -032 and class PR_RELEASE most probably, check Char. tab).
    Once you define char. in CL02, you gotta run tcode CT04, give the name of char. and fill all tab.
    inside tab Addl data, you have to define CEKKO table and field too
    this is where we have referenced the event releasestepcreated implicitly.
    FOR all customizing of release strategy check this link , this is really great blog
    http://www.sap123.com/forumdisplay.php?s=cced678eca43fe7a7e3bb9b83dc94022&f=2
    then search for "setting up simple release procedure" thread in it.
    It is for PR.
    So if I1 release take place event will triggered, say A has approved I1 level and for whole PO release I2 is also required then one more time event releasestepcreated event would be triggered.
    You can create workflow for PO release. Approver are determined based on rule AC20000026 (check in PFAC) based on FM  which has user exit EXIT_SAPLEBNF_001 where you can write down your own code for approver determination.
    I think that you gotta put 9 (in release code settting in SPRO). If you are inserting 1 then you have to define US and user name (which I think you have done).
    Hope it will clear your doubts
    Cheers
    Jai

  • Workflow for MM purchase Requisition steps required

    Dear all,
            I am trying to configure purchase requisition Workflow.
            I am working with Work flow, WS 00000038
            I have assigned agents to TS 20000162
            Now how to proceed further, do i need to maintain some more settings
            or i should try to test system.
            Regards,
            Gaurav sood

    Under the assumption that things have not changed much since 4.70, here's quick introduction:
    The workflow is started only when a relevant release strategy is found, so customizing of release strategies is a very important (first) step here.
    In the Implementation Guide you find the customizing in the following path:
    Materials Management
    -- Purchasing
    -- -- Purchase Requisition
    -- -- -- Release Procedure
    -- -- -- -- Procedure with Classification
    Only the procedures with classification are relevant if you want to use workflow to notify about requisitions waiting for release.
    First you must set up a classification class if that has not already been done. Derive your characteristics from the structure CEBAN. The online help is not too bad, I had never set up classifications before and managed to get it working.
    If you need data that are not available in CEBAN, or you want to modify them for the purpose of determining the release strategy there is an enhancement you can implement, and there are customer fields you can use. The enhancement definition's name is M06B0002.
    As an example of what you can do, I have used it to set the company code in one of the customer fields, and to change the account assignment type. However, whether you need this enhancement or not depends strongly on what data you use to determine your release procedures (a step in customizing you will get to later).
    When that is done you define release groups and release codes. Release codes are defined within each release group. Whether you should use one group or several groups is often a matter of choice.
    I myself prefer using several groups even if I don't have to, so long as it doesn't lead to having to define duplicate release strategies (which you will soon get to). So, if there is some characteristic that clearly separates your release strategies, e.g. the highest amount that does NOT require release etc, you can define one group for each value (group) of this characteristic.
    For instance, if some company codes require release for everything worth more than 100EUR while the default is to require release from 10.000EUR you could create to release groups. None of your release strategies will be duplicates since the value from which release is required will be different and you thus need to have that as a characteristic.
    You then check that the set-up of release indicators is OK, and then you are ready to start defining the strategies. Release stragies are defined within each release group, and use one or more release codes (two or more release indicators).
    It is fairly self-explanatory once you get into the screens. The thing to be observant about is to not define overlapping strategies, as this will prevent the solution from working.
    When you are done, and have tested the solution in DEV it is time to transport it to the QA system. That's when I got a rather unpleasant surprise. The classification data are not transported, so both the characteristics and class, as well as the classification data in each release strategy had to be redefined. And in roughly two hours I have to do it again in production.
    It is possible to transport classification information, it is described in SAP OSS Notes (different solutions for different versions).

  • Table for Purchase Requisition Item Text

    I would like to know, what is the table which stores the item text in tab texts for Purchase Requisition?

    Hai,
    the table is STXH.
    CALL FUNCTION 'READ_TEXT'
          EXPORTING
      CLIENT                        = SY-MANDT
            ID                            = IT_STXH-TDID "ID
            LANGUAGE                      = IT_STXH-TDSPRAS " LANGUAGE
            NAME                          = IT_STXH-TDNAME
            OBJECT                        = IT_STXH-TDOBJECT
      ARCHIVE_HANDLE                = 0
      LOCAL_CAT                     = ' '
    IMPORTING
      HEADER                        =
          TABLES
            LINES                         = L_LINES
    Regards,
    Venkat

Maybe you are looking for