Selective activation of classic scenario

Dear Experts,
One of my client has globally activated extended classic scenario. Now, they want to activate classic scenario for one particular product category. How they will achieve that?
Which BAdi they need to take care? Is BBP_Determine_logsys is enough?
thanks and regards,
Ranjan

Hi, we have implemented BBP_EXTLOCALPO_BADI, and when we create PO from SOCO everything works fine.
But when we create PO from vendor Bid, with "Create PO" button the BADI BBP_EXTLOCALPO_BADI doesn´t execute.
Can you help me please?
Thanks in advance.
Best Regards.

Similar Messages

  • Number range for extended classic scenario

    Hi,
    we've activated extended classic scenario for some defined categories (material groups), other will use classic scenario as before. It works, we are able to craete POs in both ways. I've tried to use the same number range for backend POs and for local POs. I've set the same number for both ranges but only the one which is used is getting updated. Is it possible to syncronize these ranges so backend POs will all be created in the same range?
    Regards
    Hubert

    Hi Hubert,
    Not the best practice that you are following. it might work for some time  but will fail for most of the time . The maintenance is going to be huge and you could expect problem with these.
    I would suggest not to think on the solution of same number range itself.
    Thanks
    Iftekhar Alam

  • Select type of PO in classic scenario.

    We have SRM 7.0 EHP 1 and ECC 6.0 EHP 4 in classic scenario.
    Our process begins with a shopping cart, always. The Shopping cart are sent to SOCO, where the buyer can create a RFX or a PO.
    The problem we have is that we can not select any PO that we need to generate in ECC, it always generates ECPO. We need to create such orders ZECP own, for example.
    Is it necessary to implement a BADI to select the PO available in ECC?
    Regards

    Hi,
    In the standard system for classic PO's the document type as per standard are not displayed in the dropdown in the Sourcing Cockpit.
    For extended classic they are retrived from the users organisational attribute settings.
    For fruther info please see KBA/note : 
    1580116: Classic scenario: Transaction types in Step 3 of the Sourcing Cockpit
    I hope this helps
    Kind Regards
    Lisa

  • Impact of activating IPC in classic scenario

    Hi All,
    We are in the process of implementing SAP SRM Bidding application and we are into SAP SRM 7.01 version with SP012.
    We are running in classic scenario.
    In case of bidding, in responsee comparison screen - the base price will be displayed along with freight price as net price. For eg base price is 100 and freight is 2% the net price would be 102 and the same is displayed in the std SAP SRM bid comparison screen. However when we implement the bidding engine to our client system, the bid comparison screen net price displays only the base price and freightht is not taken intoaccount. On analysis we found IPC is not activated and only Classic Light pricing is active. We believe this issue would resolve if we activate IPC.
    Can anyone please suggest what would be the impact if we activate the IPC for classic scenario?
    Your earlier response would behighly appreciated.
    regards
    Sundar

    Hi Sundar,
    Activating IPC is always suggested in SRM, simplified pricing(classic light) is actual the exception scenario as far as I know.
    You always have the option to change from simplified pricing to normal pricing using IPC. You can change from IPC pricing back to simplified pricing as well.
    Regards,
    Vidya

  • Extended Classic Scenario - SHC: Buffer table not up to date

    Hello all,
    I'm working in SRM_SERVER 550, SAPKIBKT11, and having issues using BACKEND PURCHASING ORGANISATIONS and the Extended Classic Scenario.
    According to SAP note 944918 the following indicator should not be required to be set:
    Supplier Relationship Management>SRM Server>Cross-Application Basic Settings>Activate Extended Classic Scenario --> extended classic scenario active.
    I did set the Backend Purch. Grps Responsible indicator, and I did create organizational units specifically for the backend purch. grps.
    We need to set the main part of all SHCs to ECS, but when I do set the indicator in customizing to "extended classic scenario = active", I get a dump in my web environment: 'buffer table not up to date'.
    What is causing this failure in my SHC?
    I tried to implement BAdI "BBP_EXTLOCALPO_BADI" (method DETERMINE_EXTPO) like described below here: without the line bbp_extpo_gl-bbpexpo = 'X'., I can continue and create the SHCs. Problem is though: all SHCs will get marked as Classic Scenario. So, to make sure the SHCs will always get marked as ECS, I have added this line in the BAdI. Unfortunately this immediately results in the 'buffer table not up to date' error in the SHC itself, as soon as I try to open the details of the new item.
    Hope you help me out here?? It doesn't seem to be related to the BAdI, but somehow the system doesn't allow me to mark SHC items as ECS.
    Thanks & Regards,
    Berend Oosterhoff
    SRM Consultant Accenture Technology Solutions - The Netherlands.
    BAdI BBP_EXTLOCALPO_BADI:
    method IF_EX_BBP_EXTLOCALPO_BADI~DETERMINE_EXTPO.
    data definition----------------------------------------------------*
      DATA:    wa_mattype     TYPE BAPIMATDOA,
               wa_char18      TYPE MATNR,
               attrib_tab     TYPE TABLE OF bbp_attributes,
               wa_attrib_tab  TYPE bbp_attributes,
               wa_value       TYPE om_attrval,
               wa_product_id  TYPE comt_product_id.
        bbp_extpo_gl-bbpexpo = 'X'.
    from here I did the specific selection for the SC, but that's not relevant here.

    Hi Prashant,
    Thanks for your quick reply!
    Note 1085700 is about Short Dumps when creating or changing a contract. I am trying to create a Shopping Cart, without a reference to a contract. BAdI BBP_DOC_CHANGE_BADI is not active in our system.
    Any other thoughts?
    Regards,
    Berend

  • Activate extended classic scenario

    Hello, when I try to activate extended classic scenario to create contracts in SRM and then transfer them to R/3 I have these options:
    Extended local PO
    BE Purch Grps Resp.
    Back-end check reqd
    Back-end errors, show as error msg
    Which options may I have to select?
    Thanks in advance

    Hi,
    I think Rosa's requirement is to create a manual and local contract in SRM.  Indeed you mentioned an excellent  BADi, but my understanding is this badi gets called from the sourcing application.  I am not sure whether this gets called from the SRM local contract.  This is the help documentation I am pasting here.  It would be wonderful if this works.  See the highlighted "importing parameters" part of the following pasted one.
    Thank you,
    DV
    Determine Target System of Contract
    Use
    With method CONTRACT_LOGSYS_DETERMINE, you can control the target system determination for contracts.
    In the standard, the Sourcing application and SAP Bidding Engine create contracts locally in SAP Enterprise Buyer . With this method, you can create a contract in the backend system instead.
    Requirements
    You are using a backend system with Release 4.6B or higher.
    You have created the logical system in activity Define Logical System
    Parameters
    Importing
    The BAdI takes this data from requirements in SAP Bidding Engine (bid) or from requirements in the Sourcing application.
    IT_HEADER
    Header structures
    IT_ITEMS
    Item structures
    IT_PARTNER
    Business partner data such as vendor or location
    IT_ORG
    Organizational data
    Changing
    In the method you can overwrite the following field:
    CV_LOGSYS
    Name of the system in which a contract is to be created.
    If this field remains empty or contains the name of the local system, then the contract is created locally.
    If this field contains the name of a backend system, then the contract is created there.
    Notes
    When coding the method, use the delivered sample coding as a guide.
    See also
    BAdI Determine Backend System / Company Code

  • Self service procurement and plan driven procurement in classic scenario

    hai friends,
    i have configured self service procurement and now i am configuring plan driven procurement in classic scenario.my doubt is suppose  a shopping cart is created and placed in a sourcing application of the professional buyer.And assume he accomplished sourcing activity and created purchase order .Now purchase order is created locally or in the backed.i am using classic scenario ,now can u tell where the purchase order is located? if i want to place that particular purchase order in SRM  it self what will i do? thanks in advance.

    Hi Chandra
    before going to select Business scenario (self service, plan driven..etc), you must freeze the technical scenario. Depends upon your technical scenario, your PO will be created .
    Where PO is created it is called leading system. It is SAP standard.
    If you were selected  Classic- Po created in R/3.- R/3 is a leading system .
    if you were select ECS- > PO will created in SRM and Copy also will be created in R/3 system. In EBP only you can edit the PO not in r/3. here SRM is a Leading system.
    regards
    Muthu

  • Backened documents are not getting updated in Classic Scenario

    Hi,
    We are using SRM 7.0 version and we are working on classic scenario where the shopping cart - RFX - Contract are created in SRM and the PO - GR - IR are created in ECC. The blackened documents which are created in ECC PO - GR and IR these documents are not getting updated in SRM system.
    Is there any business functions to be activated.

    Hi Sunil,
    You manually run report ""BBP_GET_STATUS_2" after PO is created in MM. Then check if the follow-on-docs are updated in SC.
    If it is working fine after you manully run report, you will have to properly set time to run this report automatically.
    Best Regards,
    Anu
    Edited by: Anuradha UG on May 18, 2010 8:09 PM

  • SRM 7.0  Unable to create PO - Classic Scenario.

    Hello,
    We are able to successfully create the below scenario.
    PR in ECC --> Get PR in SRM --> Start Collective processing -> Transfer to Central System (SC is created for the PR @ this time) --> Create RFx --> Rfx Response --> Create PO. (PO is created in ERP, Classic Scenario)
    We are able to get the PR & we are able to create SC successfully and the PR/ SC is available in Sourcing cocpit.
    Able to create RFx --> Rfx Response.
    Now once the RFx Response is Accepted --> We go for creating PO.
    Classic Scenario.
    The error is due to pricing - debugged and checked as mentioned in my earlier message.
    IPC pricing is switched off and the BADI for simple pricing is activated.
    Error :   " Message A BBP_PD 396 cannot be processed in plugin mode HTTP "
    But this is due to pricing is what i guess.
    Error is raised in FM "BBP_PDPRC_UPDATE".
    Kindly Suggest.
    Unable to Create PO
    Regards.
    Edited by: Purshothaman P on Jul 6, 2010 1:50 PM

    Hi,
    Please check and run the following reports (se38): BBP_CND_CUSTOMIZING_CHECK & RSVMCRT_HEALTH_CHECK and post back the results.
    Note for BBP_CND_CUSTOMIZING_CHECK also run 'Simulation of Pricing with Manual Price' (scroll down after executing the report initially).
    Also the badi information you activated tells us a lot. Although i take it that you executed and read everything that's included in the transaction information. The following sentence gives a prety doubtfull feeling for the CPPR scenario to work for your configuration:
    SAP recommends using this BAdI only in exceptional cases and only after checking thoroughly if it is compatible with the Business Scenarios used.
    Note: From what i've just read IPC has to be disabled, certain badi's etc. need to be disabled. And VMC (sap basis) has to be configured. Please view: [http://help.sap.com/SCENARIOS_BUS2008/helpdata/EN/9C/F90B7CB34A4889935D1733C6756D5B/content.htm]
    Could you also please check and provide whether 'normal' SRM classic scenarios like: SC -> PO do run within your system. Also the error and information you have provided is very little.
    Kind regards,
    Tim

  • SRM 7.0: Classic Scenario no PO is created only PR is generated

    Hi Gurus,
    I am working on SRM 7.0 - Classic scenario.
    When a shopping cart is complete in terms of price, vendor (assigned) and other required data, item stays in transfer process.
    If a SC is incomplete a PR document is created in backend without a problem but when a complete SC is oredered, the status of shopping cart remains I1111 i.e. item in transfer process. I can see in table BBP_PDBEI, backend object type (BE_OBJECT_TYPE) is correctly selected as BUS2012 and the document number of PO is also correctly selected.
    This is the case even for the SC ordered using catalog materials.
    I have checked following configuration and it seems to be ok.
    1.  'Define objects in backend system's
    2. Number ranges definition in SRM and ECC
    3. Document type attribute -BSA in PPOMA_BBP
    Configuraiton wise everything seems to be, I tried to manually transfer the SC using FM  BBP_REQREQ_TRANSFER but it does not change the status of SC it remains I1111
    RZ20 does not show any error for the SC with status I1111.
    Is there any sepcial FM to push the SC in SRM 7.0?
    Any help/tips would be highly appreciated. Thanks in advance.
    Best Regards,
    Amit

    Hi  Amit
    what is the setting here
    1. 'Define objects in backend system's
    is it a prefered vendor or fixed vendor
    update the partner function in bbp_pd here
    if it is 39 - you wil recive pr
    it is 19 you will get PO
    i am afraid , you stated that catalog sc stoo this problem but during debugging check what is the partne rfunction...
    there can be several reasons for creating PR instead of PO. Please see the FAQ note 1173815 for the possible reasons, and the guide for debugging under:
    https://wiki.sdn.sap.com/wiki/display/SRM/Howtoanalyzethefollow-ondocumentdetermination
    MOREOVER NOTE SAYS POSSIBLE REASONS ..
    Note 336658 - Purch req instead of purch order created in backend
    BR
    Muthu

  • PO is not generated for completed SC in SRM.70 classic scenario.

    Hi,
    I am working on SRM 7.0 - Classic scenario.
    When a shopping cart is complete in terms of price, vendor (assigned) and other required data, item stays in transfer process. even we are adding items from catalog.
    If a SC is incomplete a PR document is created in backend without a problem but when a complete SC is oredered, the status of shopping cart remains item in transfer process. I can see in table BBP_PDBEI, backend object type (BE_OBJECT_TYPE) is correctly selected as BUS2012 and the document number of PO is also correctly selected.
    This is the case even for the SC ordered using catalog materials.
    I have checked following configuration and it seems to be ok.
    1. 'Define objects in backend system's
    2. Number ranges definition in SRM and ECC
    3. Document type attribute -BSA in PPOMA_BBP
    Configuraiton wise everything seems to be, I tried to manually transfer the SC using FM BBP_REQREQ_TRANSFER but it does not change the status of SC it remains I1111
    RZ20 does not show any error for the SC with status I1111.
    Is there any sepcial FM to push the SC in SRM 7.0?
    Any help/tips would be highly appreciated. Thanks in advance.
    Thanks,
    Ravi

    learnt that PO number has generated in SRM and the same PO number not exist in ECC.
    check SM58 , rz20 log or Application monitor for the shopping cart.
    or monitor shopping cart click the icon follow on document and errror message must throw in 1 minutes.
    let us see .
    1. what is the settings in define backend OBJECTS
    2. check all basic data in the shopping cart - especially org data
    3. run bbp_check_consistancy report for your id?
    4. every user has the same issue?
    SEE THE RICHARDO technique
    http://wiki.sdn.sap.com/wiki/display/SRM/ShoppingCartStatusI1111-+Resubmit
    Muthu
    Report BBP_ALERT_SB_NOTTRANSFERED is available to change the status of the shopping cart item from I1111 to 'Error in transmission' (I1112) and later on, it is possible to retransfer this shopping cart from Application Monitor/Monitor Shopping Cart transactions.
    1480994  How to process a shopping cart with status I1111
    Edited by: Muthuraman Govindasamy on Jul 16, 2010 11:31 PM

  • PO error - extended classic scenario

    Hi Guys,
    I'm using SRM 5.0 with extended classic scenario...
    During creation of the purchase order locally (in SRM) I got the "error in process" status.
    My means of T-code RZ20 I got the following info to ithis error:
    context:B2B Procurement
    object name:Purchase Order
    short name: Backend application errors
    status: Active
    Alert text: PO 700..1: Call of a method or kernel Method that has not been implemented
    using Transaction BBP_PD I got the following status:
    Status: I1080
    Description: in transfer to execution system
    Do you have any idea what should I do in order to resolve this outstanding issue?
    many thanks in advance for your help.
    regards,
    Piotrek

    Hi
    Go to transaction - <b>SPAM</b> to get all the required Patch levels and other required system version details.
    <b>Meanwhile, try the following SAP OSS Notes as well -></b>
    <u>Note 508972 - Error during transfer of extended purchase orders
    Note 881650 - Duplicate transfer/output of the purchase order
    PO status in " error In Process ".
    Error in Transfer Process (Urgent )
    FOLLOW ON DOCUMENT NOT CREATED ( ERROR IN PROCESS)</u>
    Hope this will help.
    Regards
    - Atul

  • Classic scenario service PO replication

    Scenario:-
    Classic Scenario
    No  PI(Process Integration)
    No  PDP (Plant Driven Procurement) process
    Today we created new Service purchase requisition (which is never adopted for PO creation) which contains only one item(10), under this line item (10) five service Numbers…as 20000000(Line-10),20000021(Line-20),20000025(Line-30),20000033(Line-40),20000058(Line-50)
    then
    Our process:-
    Purchase Requisition(Service) Transferred from ECC to SRM - >Purchase Requisition Converted in to shopping cart in SRM> Shopping Cart goes to sourcing -> buyer
    creates RFx by adopting the Shopping Cart -> RFx is sent to bidder -> bidder will respond >RFx Response number will be created in SRM>Buyer will compare the RFx responses -> Buyer will click on the RFX response number of L1 vendor>in the RFX response screen when  he will click on the “CREATE Purchase Order”
    Issue:- why in  Service PO items are  splitted in to item-10,item-20,item-30,item-40 which is not same like in Service  PR
    Hope if above issue will solved below error message wont appear
    Error Message:-
    Materials of requisition 2100000654 item 00010 alr. ordered in full
    Message no. 06076
    Please  Find the attached screen shot
    Thanks
    Madhu

    Can you please elaborate more on this .
    from what I understand you want the SC item to not split into different PO  generally it spits based on different shipping address maintained . You can also check this in BADI ZBBP_GROUP_LOC_PO
    Below is a sample code I found from one of the earlier threads as below :
    http://scn.sap.com/message/2772557#2772557
    http://scn.sap.com/message/3155145#3155145
    http://scn.sap.com/message/2877448#2877448
    http://scn.sap.com/message/2371974#2371974
    https://scn.sap.com/thread/2026160
    https://scn.sap.com/thread/54153
    METHOD if_ex_bbp_group_loc_po~group_po.<BR>
    *------------------------------------------------------------------------------*<BR>
    * Exit Grouping of Items for Local Purchase Orders<BR>
    ** Parameters<BR>
    *ITEM_DATA  TYPE BBP_INT_ITEM_GROUP Item Data for Shopping Basket Item<BR>
    *It contains the most important item details of the shopping cart and<BR>
    *additionally in the field REFNUMBER a reference number for further<BR>
    *processing purposes<BR>
    *------------------------------------------------------------------------------*<BR>
    * Method used to group item before PO creation<BR>
    * How it work ?<BR>
    * 1/ Select extra colons from table ZPO_SPLIT_CRITER<BR>
    * 2/ Getting Compoents from existing type BBP_INT_ITEM_GROUP<BR>
    * 3/ For each line recalcul Refnumber<BR>
    **********************************************************************<BR>
    * Declarations<BR>
    **********************************************************************<BR>
    *--------------------------------------------------------------------*<BR>
    * Variable<BR>
    *--------------------------------------------------------------------*<BR>
      DATA: lt_zpo_split_criter TYPE TABLE OF zpo_split_criter<BR>
          , ls_zpo_split_criter TYPE zpo_split_criter<BR>
          , lo_struct           TYPE REF TO cl_abap_structdescr<BR>
          , lt_field_list       TYPE ddfields<BR>
          , ls_field_list       TYPE dfies<BR>
          .<BR>
    <BR>
      DATA:<BR>
        lt_item_data     TYPE bbp_int_item_group<BR>
      , ls_item_data     TYPE bbp_int_item_groups<BR>
      , ls_back_data     TYPE bbp_int_item_groups<BR>
      , ls_modi_data     TYPE bbp_int_item_groups<BR>
      , l_fname          TYPE fieldname<BR>
      , l_refnumber      TYPE refnumber<BR>
      , l_tabix          TYPE sytabix<BR>
      , l_not_empty      TYPE c<BR>
      , l_act_not_empty  TYPE c<BR>
      .<BR>
    *--------------------------------------------------------------------*<BR>
    * Field symbols<BR>
    *--------------------------------------------------------------------*<BR>
      FIELD-SYMBOLS: <lfs_refnumber>       TYPE bbp_int_item_groups-refnumber<BR>
                   , <lfs_act_refnumber>   TYPE bbp_int_item_groups-refnumber<BR>
                   , <lfs_field_value>     TYPE ANY<BR>
                   , <lfs_act_field_value> TYPE ANY<BR>
                   .<BR>
    *--------------------------------------------------------------------*<BR>
    * Constants<BR>
    *--------------------------------------------------------------------*<BR>
    *  CONSTANTS:<BR>
    *  .<BR>
    **********************************************************************<BR>
    * Process<BR>
    **********************************************************************<BR>
    * 1/ Select extra colons from table ZPO_SPLIT_CRITER<BR>
      SELECT * FROM zpo_split_criter INTO TABLE lt_zpo_split_criter<BR>
        WHERE split EQ 'X'.<BR>
      CHECK NOT lt_zpo_split_criter[] IS INITIAL.<BR>
      DELETE lt_zpo_split_criter WHERE fieldname = 'REFNUMBER'.<BR>
    <BR>
    * 2/ Getting Compoents from existing type<BR>
      lo_struct ?= cl_abap_typedescr=>describe_by_name( 'bbp_int_item_groups' ).<BR>
      CALL METHOD lo_struct->get_ddic_field_list<BR>
        EXPORTING<BR>
          p_langu                  = sy-langu<BR>
          p_including_substructres = abap_true<BR>
        RECEIVING<BR>
          p_field_list             = lt_field_list<BR>
        EXCEPTIONS<BR>
          not_found                = 1<BR>
          no_ddic_type             = 2<BR>
          OTHERS                   = 3.<BR>
      IF sy-subrc <> 0.<BR>
    *   MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO<BR>
    *              WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.<BR>
      ENDIF.<BR>
    <BR>
      LOOP AT lt_zpo_split_criter INTO ls_zpo_split_criter.<BR>
    *   Verify if field exist in table<BR>
        READ TABLE lt_field_list<BR>
             TRANSPORTING NO FIELDS<BR>
             WITH KEY fieldname = ls_zpo_split_criter-fieldname.<BR>
        CHECK sy-subrc EQ 0.<BR>
    <BR>
    *   Copy table in internal<BR>
        lt_item_data[] = item_data[].<BR>
    <BR>
    *   Sort table by REFNUMBER and fieldname<BR>
        SORT lt_item_data<BR>
          BY refnumber (ls_zpo_split_criter-fieldname)<BR>
          ASCENDING.<BR>
    <BR>
    *   Clear internal value.<BR>
        CLEAR: l_refnumber<BR>
             .<BR>
    <BR>
        CONCATENATE 'LS_ITEM_DATA-' ls_zpo_split_criter-fieldname<BR>
          INTO l_fname.<BR>
        ASSIGN (l_fname) TO <lfs_act_field_value>.<BR>
        CHECK sy-subrc = 0.<BR>
        CONCATENATE 'LS_BACK_DATA-' ls_zpo_split_criter-fieldname<BR>
          INTO l_fname.<BR>
        ASSIGN (l_fname) TO <lfs_field_value>.<BR>
        CHECK sy-subrc = 0.<BR>
        CONCATENATE 'LS_ITEM_DATA-' 'REFNUMBER'<BR>
          INTO l_fname.<BR>
        ASSIGN (l_fname) TO <lfs_act_refnumber>.<BR>
        CHECK sy-subrc = 0.<BR>
        CONCATENATE 'LS_BACK_DATA-' 'REFNUMBER'<BR>
          INTO l_fname.<BR>
        ASSIGN (l_fname) TO <lfs_refnumber>.<BR>
        CHECK sy-subrc = 0.<BR>
    <BR>
        CLEAR: <lfs_refnumber><BR>
             , <lfs_field_value><BR>
             .<BR>
    <BR>
    *   For each reccord in table, calculate new REFNUMBER<BR>
        LOOP AT lt_item_data INTO ls_item_data.<BR>
          MOVE sy-tabix TO l_tabix.<BR>
          IF <lfs_act_field_value> IS INITIAL.<BR>
            MOVE ' ' TO l_act_not_empty.<BR>
          ENDIF.<BR>
    <BR>
          IF ls_zpo_split_criter-as_not_blank IS INITIAL.<BR>
    *       Case of each value on field create a new refnumber<BR>
            IF <lfs_field_value> NE <lfs_act_field_value> OR<BR>
               <lfs_refnumber> NE <lfs_act_refnumber> .<BR>
              l_refnumber = l_refnumber + 1.<BR>
              MOVE <lfs_act_field_value> TO <lfs_field_value>.<BR>
              MOVE <lfs_act_refnumber> TO <lfs_refnumber>.<BR>
            ENDIF.<BR>
          ELSE.<BR>
            IF l_not_empty NE l_act_not_empty OR<BR>
               <lfs_refnumber> NE <lfs_act_refnumber> .<BR>
              l_refnumber = l_refnumber + 1.<BR>
              MOVE l_act_not_empty TO l_not_empty.<BR>
              MOVE <lfs_act_refnumber> TO <lfs_refnumber>.<BR>
            ENDIF.<BR>
    <BR>
          ENDIF.<BR>
          ls_modi_data = ls_item_data.<BR>
          ls_modi_data-refnumber = l_refnumber.<BR>
    <BR>
          MODIFY item_data FROM ls_modi_data INDEX l_tabix<BR>
                 TRANSPORTING refnumber.<BR>
        ENDLOOP.<BR>
      ENDLOOP.<BR>
    <BR>
    ENDMETHOD.
    <BR>
    <BR>
    <BR>
    It works with the table ZPO_SPLIT_CRITER as bellow:<BR>
    CLIENT                     MANDT<BR>
    FIELDNAME             FIELDNAME<BR>
    SPLIT                     BOOLE_D<BR>
    AS_NOT_BLANK     BOOLE_D<BR>
    <BR>
    If you need more information, contact me directly.<BR>
    Regards, <BR>
    <BR>
    David BOUTIER<BR>
    Consultant technique Sap Netweaver - KALYDIA<BR>
    8, rue Pasquier - 75008 Paris<BR>

  • Central Contract Management in case of Classic Scenario

    Hi,
    At our current implementation, requirement is to implement both Service procurement(with hierarchy) and Central Conract Management. I was exploring the possibility of utilizing Central Contract Management with Classic scenario.
    Will the Central Contracts created in this fashion be available in Sourcing Cockpit for the buyer to select against Purchase Requisitions? Will the Central Contract be visible at all in SRM in this case ?
    Please respond only with reference to Classic scenario.
    Thanks,
    Abhilash

    Yes the Central Contract will be available in the Sourcing Cockpit, both local and classic scenario's. Yes the Central Contracts will be available for the creation of Purchase Requisitions in R/3 and to assign SOS in R/3.
    Do know that for SRM 7.0 PI is required for setting up Central Contracts. This is promised to change with the release of EHP1 for SRM (due june 2010).
    Kind regards,
    Tim

  • No GR on Confirmation Approval in Extended Classic Scenario

    Hi all gurus out there,
    We are trying to implement confirmation approval workflow in our SRM system. Our SRM version is SRM 3.0 or EBP 4.0 and we are operating in extended classic scenario.
    We implement the approval workflow WS10400002 (1-step approval) and WS10400010 (no approval). WS10400002 is used in situation when an administrator does the confirmation and will go to the requestor for approval. Here, when the requestor approves the confirmation, the status is updated correctly to 'Approved' but no goods receipt is triggered by the system. We looked at the workflow and found that there is no task/activity to do the post goods receipt in the backend system.
    Can someone please confirm whether these are the correct workflows that I should be using and that it is not a bug? I just want to make sure it is not as a result of a standard limitation before going back to SAP.
    Cheers!
    Siow Fong

    Hi Guys,
    I checked with SAP on this and found out that the standard codes would have created the goods receipt. This creation is no longer coded in the workflow itself (like the old workflow used to be). The reason why it was not working for us was a piece of code being added that prevented the creation of the goods receipt.
    Regards
    Siow Fong

Maybe you are looking for