GR_NON_VAL flag setting in ECC for  SRM PO

Hi all,
SRM 5.0 ECS Sp12.
When we create a PO with multiple a/c assgt,the ECC PO which gets created always has the GR_NON_VAL flag set as "X".
Now if I uncheck the indicators "Confirmation-Related Invoice Verification " and "Confirm Performance of Service/Goods Receipt   " in SRM PO,then the PO replication fails in ECC and in SRM I get the below error :
With non-valuated GR, please also enter GR indicator
When I check the data which is passed to ECC,the GR_NON_VAL flag is also blank for the PO after the indicators "Confirmation-Related Invoice Verification " and "Confirm Performance of Service/Goods Receipt   " are unchecked in SRM PO.
Can someone let me know if in ECS , the GR_NON_VAL flag is always passed as blank and gets set to "X"based on ECC settings.If so,which settings in ECC determine the GR_NON_VAL flag to be set?
Can someone explain the istd behaviour for the GR_NON_VLAg flag in ECC PO for ECS when SRM  PO with multiple a/c assignnment is changed for indicators "Confirmation-Related Invoice Verification " and "Confirm Performance of Service/Goods Receipt   "so that they are set to blank,Please advise.

HI
in standard we canl fill the flag GR_NON_VAL in SRM side but
the itemx structure of PO in ERP system set to space. After this mapping
BAPIs will be called.
wa_bapi_poitemx-po_itemx = 'X'.
    wa_bapi_poitemx-no_more_gr = 'X'.
    wa_bapi_poitemx-final_inv = 'X'.
    wa_bapi_poitemx-gr_ind = 'X'.
    wa_bapi_poitemx-delete_ind = 'X'.
  delivery tolerance has to be taken over
    wa_bapi_poitemx-over_dlv_tol = 'X'.
    wa_bapi_poitemx-unlimited_dlv = 'X'.
    wa_bapi_poitemx-under_dlv_tol = 'X'.
  note 644721, the Goods receipt non-valuated should be set according
  to the backend customizing for this we have to clear the x-flag
    wa_bapi_poitemx-gr_non_val = ' '.
    wa_bapi_poitem-gr_non_val = ' '.
The redetermination will happen in PO create / change process
(within BAPI_PO_CHANGE and BAPI_PO_CREATE1).
1353431    ECS: PO in ERP always created with GR_NON_V
Summer

Similar Messages

  • Deletion Flag setting Error message for production order

    "Unprocessed future change recs for orders prevent del. flag/completion"
    I tried to used COFC and CO1P but didn't work out?
    How to fix this issue i am trying to set deletion flags for certain production orders?
    If i even found errors in final confirmations how to fix them

    Hi Aparna,
    This is absolutely fine to set the deletion flag to archieve the Production Orders.
    For this error, which you are getting, there could be entries in COGI or CO1P..
    Whether you are using Process Control (check in OPK4)?
    If that is the case you should have got the entries in CO1P.
    Can you see any entries in COGI? even 102 movement against the order?
    Check once again and revert for further discussion..
    Regards,
    Siva

  • Report for update of Material with deletion Flag from R/3 to SRM

    Hi All,
               Is any report for Updating material in SRM with deletion indicator for those  deletion flag set in R/3...

    Check material status
      IF mat_mmsta EQ '--'.
        lv_msgv1 = iv_ordered_prod.
        CALL FUNCTION 'BBP_PD_MSG_ADD'
          EXPORTING
            i_msgty       = c_msgty_e
            i_msgid       = 'BBP_PD'
            i_msgno       = 426
            i_msgv1       = lv_msgv1
          EXCEPTIONS
            log_not_found = 1
            OTHERS        = 2.
        IF sy-subrc <> 0.
          PERFORM abort.
        ENDIF.
        IF c_on = c_off.
          MESSAGE e426(bbp_pd) WITH lv_msgv1.
        ENDIF.
      ENDIF.
      if not mat_lvorm is initial.
        lv_msgv1 = iv_ordered_prod.
        call function 'BBP_PD_MSG_ADD'
    program name LBBP_PDIGPF2R
    Check material in backend
      CALL FUNCTION 'META_MATERIAL_READ'
        EXPORTING
          i_mtcom        = ls_mtcom_eci
          logical_system = iv_log_system
        IMPORTING
          e_mmsta        = mat_mmsta
          e_lvorm        = mat_lvorm
        EXCEPTIONS
          mat_not_found  = 1
          OTHERS         = 2.
      IF sy-subrc <> 0.
        lv_msgv1 = iv_ordered_prod.
        lv_msgv2 = iv_plant.
        CALL FUNCTION 'BBP_PD_MSG_ADD'
          EXPORTING
            i_msgty       = c_msgty_e
            i_msgid       = 'BBP_PD'
            i_msgno       = 275
            i_msgv1       = lv_msgv1
            i_msgv2       = lv_msgv2
          EXCEPTIONS
            log_not_found = 1
            OTHERS        = 2.
        IF sy-subrc <> 0.
          PERFORM abort.
        ENDIF.
        IF c_on = c_off.
          MESSAGE e275(bbp_pd) WITH lv_msgv1 lv_msgv2.
        ENDIF.
      ENDIF.
          EXPORTING
            i_msgty       = c_msgty_e
            i_msgid       = 'BBP_PD'
            i_msgno       = 345
          EXCEPTIONS
            log_not_found = 1
            others        = 2.
        if sy-subrc <> 0.
          perform abort.
        endif.
        if c_on = c_off.
    IN SRM PROGRAM LBBP_PDIGPF2R BBP_PD 345 throws message "product x is designed for deletion"
    but it is validationg from fm 'META_MATERIAL_READ'
    please close this thread
    br
    muthu

  • POD flag set up automatically after BP replicated from CRM to ECC

    Hi Experts,
    we are working on CRM 5.0 and ECC 6 as backend system.
    *Requirement :*We will create a BP record in CRM and the same will be replicated to ECC.For the BPs which is replicated to ECC from CRM , the "Relevant for POD "(Proof of Delivery) flag should set up automatically.
    Note: we have done the following settings
    1) Created a Reference Customer in ECC in which we have set up a flag "Relevant for POD ".
    2) Initial download Reference BP from ECC to CRM by going to TCode:CRMC_BUPA_CONSUM in CRM.
    3) Maintained relevant Sales Areas for the BP.
    Question:
    In CRM we dont have field called "Relevant for POD ".How can we populate the field "Relevant for POD " for the Business Partner that is Created in CRM and replicated to ECC?
    For any helpful answer points will be awarded.
    Thanks in advance,
    -Rahul.
    Edited by: rahul biji on Feb 12, 2008 6:21 PM

    Hi,
    did you find a solution to make this work ? We have the same problem with other fields that are only available in R/3. We are thinking of adding a FM to fill these fields in table COM_BUPA_CALL_FU. Did you find another way ?
    Best regards
    Annette

  • Net price zero for SRM service central contract in SAP ECC

    Hi
    Net price in backend ECC is showing as zero for SRM service central contrracts, all other price fieids are fine expect net prices. We have no issues for material contract.
    Does any one had similar issue of net price zero? I have tested this scenrio in couple of SRM 7 landscpape all are with similar behaviour. Is it standard?
    Your response is highly appreciated.
    Regard
    Prashanth K Saralaya

    Hi prashant
    I never tried service . but you can see this below symptom for you.I extensively worked on Material contracts.
    Are you creating contract from Process contract or Via RFQ
    Note 1272305 - Total value wrongly calculated in Contract Service lines
    Symptom
    We create a Service contract in the R/3 Backend from RFQ. During the transfer we calculate the gross price based on the quantity,price and price unit. (ie) The field ESLL-BRTWR is filled with following formula in the idoc processing. ls_e1edc20-BRTWR
              = ( is_item-price * is_item-quantity ) / is_item-price_unit.
    AS total value of the service lines is calculated based on the field NETWR which is passed as blank from SRM, during recalculation total value when we change the gross price of one of the service lines in r/3, it is required to fill this field
    till PI values are brought correctly till posting to ECC. ?
    Note 1123292 - Net Price wrongly calculated in plug-in MAP_BLAORD_SERVICES
    my experience in GOA
    Note:-
    2 set stream of DATA comes from SRM as BLOARD and COND_A ..
    Even some times when we reprocess failed IDOCS in BD87 in ECC ( comes contract data from SRM as GOA and failed due to some data validation in ECC). now data issue was fixed at Material master level. and
    if we forget to reprocess COND_A - BLOARD creates a successfull GOA but net price shows as ZERO for each material and when you post the COND_A data and correct price will be updated in ECC contract. so kindly check price data reaches or not not or price calculation failed in ECC.
    Muthu

  • Vendor Migration issue for SRM as add-on to ECC

    Hello Experts,
    I am working on SRM as add-on to ECC.
    When I am trying to migrate vendors from ECC to SRM using MDS_LOAD_COCKPIT. Within monitor, all queues are 'green' indicating that data has successfully migrated to SRM.
    But when I check vendors in trx- ppomv_bbp, i don't see any vendor being migrated from ECC. Neither the BPs are crated for these vendor masters.
    I have configured all necessary configuration- i.e.
    1) I have carried out necessary settings in tables-
    mdsv_ctrl_opt_a
    crmc_but_call_fu
    v_tbc001
    2) In addition, I have maintained backend Purchase Org in PPOMA_BBP.
    3) I have checked RFC connections, definition of logical systems and
    it seems to be alright.
    Can anybody please guide if I am missing on any config or can point
    me in right direction to investigate??
    At SRM GUI, I tried making a local vendor using 'BBPMAININT' but end up in a short-dump.
    Can you please help?
    Thanks and Regards,
    Amit

    Hi,
    if you problem is still existing, following might be possible solution. Try it.
    Maintain Table BBP_MARKETP_INFO with corresponding Vendorroot ID (ex. VG50000....) that you already created in the PPOCV_BBP trx.
    Hope it helps.
    Regards
    PM

  • SRM "one-client" installation on ECC 6.0 EhP: Own client needed for SRM?

    Hello experts,
    i've a question concerning the SRM "one-client" installation on ECC 6.0 EhP4 as Add-On.
    Is it possible to use SRM and ERP funtionality in a single client e.g. 001?
    Or do we have to use different clients on the system like for SUS?
    I haven't found any information regarding this topic in SAP ressources. I'm currently using CG "SAP SRM on One Client in
    SAP ERP" Release date 2008 (found on marketplace/srm-inst --> srm7.0); SRM - Technical Basis Configuration (BuildingBlock S00/S03). I'm facing problems while going through the following customizing steps:
    Assign logical System to Client [both logicall systems are on the same client (001)] ==> error while trying to reference the second logical sys. because client (001) cannot be used again (own presumption: error message differs)
    I've seen that some of you have successfully installed and customized this szenario. If someone could provide me any helpful information or guideline how to proceed in general... would be great...
    Best regards,
    PATRICK

    Thanks for your reply. I've checked the offline documentation because i've no access to solman.
    There is a document which describes the steps for configuring one-client customizing on marketplace.
    Link: [SAP SRM 7.0: SAP SRM on One Client with SAP ERP|https://websmp203.sap-ag.de/~sapidb/011000358700001201562009E]
    The problem is that its impossible to cofigure the system like it's described in the document.
    Let me explain why...
    SRM Addon is installed and customizing is done in client 001 (same client as erp)
    overview about defined logical systems:
    -ONECLNTERP (for ERP is defined)
    -ONECLNTEBP (for SRM is defined)
    When I try to assign the logical system to client 001 it works for the first entry
    for the second log. system it shows up an error message.
    -->I assume because client 001 has been already assigned. I cant use client 001 again.
    But One-Client szenario schould be possible in a single client or is SAPs One-Client more like One-System with differnet clients for SRM and ERP on the same machine?
    Because of the above mentioned problem I assume that it's impossible to run ERP and SRM in the same Client number.
    Am I right? Do I have to use two Clients on One System for proper Customizing?
    Or if it's possible to use a single client on one machine for both ERP and SRM how is it possible to assign two log. systems to one client number?
    I'm totally confused. Any help would be appreciated  - any tips/hints/experiences from someone who has customized One-Client?
    BR, Patrick

  • No Business Partner generated for new employee transfer from ECC to SRM

    Hi All,
    I am working on SRM 5.0 with ECC 6.0 backend. The HR structure is replicated from ECC using ALE, message type:HRMD_ABA.
    When I am trying to replicate a new employee from ECC to SRM, I run the O-insert first, then the S-insert and then the P-insert using PFAL transaction.
    The Org structure was already in place in SRM, so it just adds the new position to it by A003 relation. The S-insert generated idoc shows status as '53' in both ECC and SRT with the relation A003, B007 and A008. But, when I check the table HRP1001, the A008 entry is missing. Due to this, no CP is generated for this position and also no business partner is generated for this user.
    When I run the P-insert for this employee, the idoc is posted in ECC. But, the status of the idoc in SRT is '52' and the message shown is "The Parameter Country Has Not been Entered During Naming Format Check" Message No. R11206.
    I checked the Name Format for this employee, and it is maintained as 2.
    Where am I going wrong? Why is no CP person generated even when the idoc status is 53? Why isn't the new employee getting transferred to SRM server?
    I have checked the SAP notes related to HR-ECC Org transfer, but I am unable to figure out the reason for this problem.
    Could anyone help me out in this?
    Regards,
    Ancy

    Maintained the name format tables (SA13)on ECC and SRM side.

  • What are the additional steps for SRM refresh as compared to ECC refresh? (Windows and MS SQL)

    Hi,
    I need to know if there are any additional pre steps or post steps for SAP SRM system refresh as compared to SAP ECC refresh? Windows/MS SQL

    Hello Rajat,
    You have to change all the data on the middleware configuration tables to point to your new ECC system. I don't remember exactly which tables are but you can take a look to this:
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/309258e9-0da2-2d10-b598-bf27edb56a31?overridelayout=t…
    It explains how to do the Middleware Configuration between SRM and ECC. You should also do a master data transfer from ECC to SRM.
    Best regards.

  • Dirty flag set for readonly file page

    We are using BDB 4.8.26 transactional data store on Windows 2008 R2.
    DB is logging the message "dirty flag set for readonly file page" to the error log ... this entry was logged 17 times in a 24 hr period. The system processes about 3-5 requests a second.
    We also are having an incorrect "SECONDARY inconsistent with primary" error reported - this used to be very rare but has increased with increased concurrency. But the dirty flag error is recent - after we dropped a secondary and added a new one - there was no error during the secondary drop and rebuild process.
    Appreciate any help on this.
    Thanks
    Kimman Balakrishnan

    Hi Kimman,
    I assume you are not opening your databases with the DB_RDONLY flag. This could be cause by not running recovery after a system or application failure. Make sure you run recovery correctly, single threaded, after each system or application failure; review the Architecting Transactional Data Store applications documentation section.
    Regards,
    Andrei

  • Advantages and disadvantages for SRM on one client with ECC

    Dear SAP gurus,
    We are evaluating the use of SRM on one client with ECC. Is there a paper spesifally discuss the advantage and disadvantages of having this deployment option?
    Best regards,
    John

    Hi
    check this  link
    SRM Server as an Add on to ERP 2005
    Advantages
    1) one backend for SRM and ECC6.0
    Disadvantage
    1.Sourcing scenario cannot be implemented.
    2.It does not support multiple backend system.
    Regards
    G.Ganesh Kumar

  • GR Based INV flag set on Purchase Order

    Hello,
    We are on SRM 5.5 and R3 ECC 6.0 classic scenario. We want to swihtch off the GR Based Invoice flag which is maintained in de vendor master. Vendor has no info record or contract. When creating a PO directly in R3 the flag is also disabled on the PO. However, when we create a shopping cart, the system automatically creates the purchase req and when the purchaser creates the Purchase order the GR Based Inv. flag is set again ? Can anybody let me know how this is possible ?
    Thanks as eve for your help.
    Antoinette

    Hi Antoinette Stork,
    Here is the way we have achieved. I am not an ABAPer and hence providing you more concepts than code.
    01)  A custom program is written and is scheduled on hourly basis as a back ground job.
    02)  This program is executed after the BBP_VENDOR_SYNC is executed as a background job as well.
    03)  BBP_VENDOR_SYNC will bring the updates and new vendors from the R/3 back end.
    04)  This will bring the vendors with the confirmation flag set on SRM (no corresponding field exists on the R/3 side vendor master) and also will check the GR based invoice verification flag on (the corresponding field exists on the ECC vendor master).
    05)  After 15 minutes the custom program will read the BUT000 table for the total number of vendors changed or created between two successive jobs.
    06)  Then query on the VENMAP table to get the GUIDs of the corresponding vendors.
    07)  Within the custom program use the FMs
         BBP_BUPA_FRG0060_CHANGE  and
         BAPI_TRANSACTION_COMMIT
    to set the flags for
          goodsrec_confex = ' '  and
          GR_BASEDIV
    Sorry for being unable to provide you the code dump.  This is working perfectly fine for us.
    Also, we have used the badi "BBP_ECS_PO_OUT_BADI"  with the method "BBP_B46B_PO_OUTBOUND"  as a safety net as our invoice processing is two way match and we do not absolutely want the flags to be set to the R/3 PO.
      DATA: ls_bapi_poitem TYPE bbps_if_bapimepoitem_pi.
    Loop through the item details that gets passed to Backend*
      LOOP AT ct_bapi_poitem INTO ls_bapi_poitem.
    Clear the GR and GR-Based Invoice Verification Indicator.*
        CLEAR : ls_bapi_poitem-gr_ind,
                ls_bapi_poitem-gr_basediv.
        MODIFY ct_bapi_poitem FROM ls_bapi_poitem
               TRANSPORTING gr_ind gr_basediv.
      ENDLOOP.
    ENDMETHOD.
    Hope this helps,
    DV

  • Configure partial invoice distribution for SRM Purchase Order

    Hello Experts,
    We are on SRM 5.0 SP12 and ERP 6.0 SP13.  When a split accounting purchase order is created in SRM and transfers over into SAP, partial invoices are automatically posting with the distribution of "Distribute to following row".  In ME23N under account assignment, there are three options for partial invoice postings:
    1) Derive from account assignment category
    2) Distribute to following row
    3) Distribute proportionally
    We would like to default the third selection, "Distribute proportionally".  Does anyone know where this setting can be changed or how to do this?
    Thanks,
    Brett

    SAP was able to provide assistance on the issue. Here are the details:
    The SRM always sends to ECC the "Distribute to Following Row" selected,
    and sometimes configuration changes in tcode OME9 have not effect,
    possibly due to the Support Package.
    To specify the correct option "Distribute Proportionally", it is necessary to use the Badi BBP_PO_INBOUND_BADI...
    The partial invoice indicator is set to '1' by default in SRM, it is
    standard behaviour, you can check it in the LBBP_BD_DRIVER_46AF15
    program. The functionality that allow has the value ´2´ to partial
    invoice indicator is exclusive to MM - R3 system.
    You have two possible solution to create from EBP to backend some PO
    documents with multiple account assignment and partial invoice
    indicator = 2 (Distribute Proportionally):
    a) To use the Badi BBP_ECS_PO_OUT_BADI to create the PO this way.
    ls_ct_bapi_poitem-PART_INV = '2'
    Effectively, this solution change the setting in the backend
    to 'Distribute Proportionally'.
    b) Partial invoice indicator can either be set in OME9 in the Backend
    for the posted account assignment category (e.g. K - cost center)
    or default using Backend Badi:
    BBP_PO_INBOUND_BADI
    BBP_POITEM-PART_INV
    -> Part_INV is a field of BBP_POITEM. In the backend BADI, if you
    look at the field of BBP_POITEM, you will find PART_INV. You
    have to use the BADI to set this field.
    OME9 was the tcode in MM to specify the partial invoice settings for each account assignment. According to SAP, sometimes this works with SRM (since the default setting sent to ECC from SRM is "Distribute to following row") and sometimes it doesn't. We ended up changing the partial invoice flag upon creation of the purchase order through the BADI mentioned above since the configuration changes did not remedy the issue. Now the partial invoices are posting proportionally which has resolved all of our split accounting posting issues.
    Thanks,
    Brett

  • ECC to SRM Issue

    Hi experts,
    we are doing ECC to SRM Integartion using SAP XI.
    ECC to XI - IDOC
    XI to SRM - ABAP Proxies
    Scenario : VEndor data migaration
    We are transfering vendor data to SRM using SAP XI using BD14 T.code in ECC.
    IDOC generated in ECC and transfered to XI successfully and from XI message send to SRM successfully. In SRM , It is throwing an error in SXMB_MONI .
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Inbound Proxy
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIProxy</SAP:Category>
      <SAP:Code area="ABAP">DYNAMIC_CALL_FAILURE</SAP:Code>
      <SAP:P1>UNCAUGHT_EXCEPTION</SAP:P1>
      <SAP:P2>CL_BBPX_TRADING_PARTNER_SUS_IN</SAP:P2>
      <SAP:P3>EXECUTE_ASYNCHRONOUS</SAP:P3>
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error during proxy processing An exception with the type CX_BBPX1_STD_MESSAGE_FAULT occurred, but was neither handled locally, nor declared in a RAISING clause Application Error</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    As we used CREMAS As IDOC in ECC and Standard ABAP proxy ( Std class ) at SRM side.
    as i tested the class manually it is throwing into dump.
    Runtime Errors         OBJECTS_OBJREF_NOT_ASSIGNED_NO
    Exception              CX_SY_REF_IS_INITIAL
    Date and Time          13.12.2008 17:36:42
    Short text
    Access via 'NULL' object reference not possible.
    What happened?
    Error in the ABAP Application Program
    The current ABAP program "CL_PROXY_INBOUND_ADAPTER======CP" had to be
    terminated because it has
    come across a statement that unfortunately cannot be executed.
    What can you do?
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
    Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not
    caught in
    procedure "SET_METHOD" "(METHOD)", nor was it propagated by a RAISING clause.
    Since the caller of the procedure could not have anticipated that the
    exception would occur, the current program is terminated.
    The reason for the exception is:
    You attempted to use a 'NULL' object reference (points to 'nothing')
    access a component.
    An object reference must point to an object (an instance of a class)
    before it can be used to access components.
    Either the reference was never set or it was set to 'NULL' using the
    CLEAR statement.
    How to correct the error
    Probably the only way to eliminate the error is to correct the program.
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "OBJECTS_OBJREF_NOT_ASSIGNED_NO" "CX_SY_REF_IS_INITIAL"
    "CL_PROXY_INBOUND_ADAPTER======CP" or "CL_PROXY_INBOUND_ADAPTER======CM00I"
    "SET_METHOD"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
    To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
    Display the system log by calling transaction SM21.
    Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
    In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.
    The exception must either be prevented, caught within proedure
    "SET_METHOD" "(METHOD)", or its possible occurrence must be declared in the
    RAISING clause of the procedure.
    To prevent the exception, note the following:
    System environment
    SAP-Release 700
    Application server... "SRMSUS"
    Network address...... "190.3.90.122"
    Operating system..... "Windows NT"
    Release.............. "5.2"
    Hardware type........ "4x Intel 801586"
    Character length.... 8 Bits
    Pointer length....... 32 Bits
    Work process number.. 2
    Shortdump setting.... "full"
    Database server... "SRMSUS"
    Database type..... "ORACLE"
    Database name..... "SRD"
    Database user ID.. "SAPSRD"
    Char.set.... "English_United State"
    SAP kernel....... 700
    created (date)... "Oct 6 2008 01:42:27"
    create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
    Database version. "OCI_10201_SHARE (10.2.0.1.0) "
    Patch level. 180
    Patch text.. " "
    Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
    SAP database version. 700
    Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
    NT 6.0"
    Memory consumption
    Roll.... 8112
    EM...... 18815328
    Heap.... 0
    Page.... 114688
    MM Used. 2421664
    MM Free. 712664
    User and Transaction
    Client.............. 500
    User................ "MCL-1744"
    Language key........ "E"
    Transaction......... "SPROXY "
    Transactions ID..... "7C0EC9DD9C02F137A21C00065BF30D3E"
    Program............. "CL_PROXY_INBOUND_ADAPTER======CP"
    Screen.............. "SAPLSPRX_SI_TEST 0500"
    Screen line......... 10
    Information on where terminated
    Termination occurred in the ABAP program "CL_PROXY_INBOUND_ADAPTER======CP" -
    in "SET_METHOD".
    The main program was "SPROX_SERVICE_INTERFACE_TEST_I ".
    In the source code you have the termination point in line 59
    of the (Include) program "CL_PROXY_INBOUND_ADAPTER======CM00I".
    The termination is caused because exception "CX_SY_REF_IS_INITIAL" occurred in
    procedure "SET_METHOD" "(METHOD)", but it was neither handled locally nor
    declared
    in the RAISING clause of its signature.
    The procedure is in program "CL_PROXY_INBOUND_ADAPTER======CP "; its source
    code begins in line
    1 of the (Include program "CL_PROXY_INBOUND_ADAPTER======CM00I ".
    Source Code Extract
    Line
    SourceCde
    29
    nsuri = lv_uri
    30
    31
    32
    lv_name = registry->response_msg_name.
    33
    lv_uri  = registry->response_msg_namespace.
    34
    me->response_part = cl_sxmlp_factory=>create_data_st(
    35
    name = lv_name
    36
    nsuri = lv_uri
    37
    38
    39
    lv_extended_xml_handling = get_extended_xml_handling(
    40
    method            = me->framework->if_proxy_framework~r3_method
    41
    message_direction = if_wsprotocol_payload=>co_message_direction_request
    42
    43
    lr_stylesheet_runtime = framework->get_stylesheet_runtime( lv_extended_xml_handling ).
    44
    45
    lt_signature = lr_stylesheet_runtime->get_signature( ).
    46
    loop at lt_signature assigning <signature>.
    47
    if <signature>-decl = sprox_const_dir_importing or
    48
    <signature>-decl = sprox_const_dir_exporting or
    49
    <signature>-decl = sprox_const_dir_changing.
    50
        create abap data
    51
    create data lr_data_ref type (<signature>-typename).
    52
        add it to abap parameters
    53
    lv_abap_param-name  = <signature>-param.
    54
    lv_abap_param-value = lr_data_ref.
    55
    insert lv_abap_param into table abap_params.
    56
    case <signature>-decl.
    57
          add it to according part
    58
    when sprox_const_dir_importing.
    >>>>>
    me->request_part->add_data_ref( name = <signature>-param data_ref = lr_data_ref ).
    60
    when sprox_const_dir_exporting.
    61
    me->response_part->add_data_ref( name = <signature>-param data_ref = lr_data_ref )
    62
    lv_need_response_part = 'X'.
    63
    when sprox_const_dir_changing.
    64
    me->request_part->add_data_ref( name = <signature>-param data_ref = lr_data_ref ).
    65
    me->response_part->add_data_ref( name = <signature>-param data_ref = lr_data_ref )
    66
    lv_need_response_part = 'X'.
    67
    endcase.
    68
    endif.
    69
    endloop.
    70
    71
    me->is_synchron = lv_need_response_part.
    72
    73
    if lv_need_response_part <> 'X'.
    74
      response part must not be provided for there are no output parameters
    75
    clear me->response_part.
    76
    endif.
    77
    78
    make sure that proxy class is created
    Contents of system fields
    Name
    Val.
    SY-SUBRC
    0
    SY-INDEX
    0
    SY-TABIX
    1
    SY-DBCNT
    1
    SY-FDPOS
    1
    SY-LSIND
    0
    SY-PAGNO
    0
    SY-LINNO
    1
    SY-COLNO
    1
    SY-PFKEY
    MAIN
    SY-UCOMM
    SY-TITLE
    Test Service Provider: Display Request
    SY-MSGTY
    SY-MSGID
    SY-MSGNO
    000
    SY-MSGV1
    SY-MSGV2
    SY-MSGV3
    SY-MSGV4
    SY-MODNO
    2
    SY-DATUM
    20081213
    SY-UZEIT
    173642
    SY-XPROG
    SAPMSSY1
    SY-XFORM
    XAB_READ
    Active Calls/Events
    No.   Ty.          Program                             Include                             Line
    Name
    9 METHOD       CL_PROXY_INBOUND_ADAPTER======CP    CL_PROXY_INBOUND_ADAPTER======CM00I    59
    CL_PROXY_INBOUND_ADAPTER=>SET_METHOD
    8 METHOD       CL_PROXY_INBOUND_ADAPTER======CP    CL_PROXY_INBOUND_ADAPTER======CM00L    10
    CL_PROXY_INBOUND_ADAPTER=>IF_PROXY_INBOUND_ADAPTER~SET_METHOD
    7 METHOD       CL_PROXY_ADAPTER_TEST=========CP    CL_PROXY_ADAPTER_TEST=========CM001    61
    CL_PROXY_ADAPTER_TEST=>INBOUND_TEST
    6 METHOD       SPROX_SERVICE_INTERFACE_TEST_I      SPROX_SERVICE_INTERFACE_TEST_I        162
    LCL_SI_TEST=>IF_PROXY_SI_TEST~EXECUTE
    5 FORM         SAPLSPRX_SI_TEST                    LSPRX_SI_TESTF01                      341
    EXEC
    4 FORM         SAPLSPRX_SI_TEST                    LSPRX_SI_TESTF01                      222
    USER_COMMAND_0500
    3 MODULE (PAI) SAPLSPRX_SI_TEST                    LSPRX_SI_TESTI01                       22
    USER_COMMAND_0500
    2 FUNCTION     SAPLSPRX_SI_TEST                    LSPRX_SI_TESTU01                       14
    SPRX_SI_TEST
    1 EVENT        SPROX_SERVICE_INTERFACE_TEST_I      SPROX_SERVICE_INTERFACE_TEST_I         97
    START-OF-SELECTION
    Chosen variables
    Name
    Val.
    No.       9 Ty.          METHOD
    Name  CL_PROXY_INBOUND_ADAPTER=>SET_METHOD
    REGISTRY
    E0001000
    2000D100
    REQUEST_PART
    |
    | F0000000 |
    | F0000000 |
    | LT_SIGNATURE |
    | Table IT_894[1x879] |
    | CLASS=CL_PROXY_INBOUND_ADAPTERMETHOD=SET_METHODDATA=LT_SIGNATURE |
    | Table reference: 90 |
    | TABH+  0(20) = E078CC51C827D051000000005A0000007E030000 |
    | TABH+ 20(20) = 010000006F0300004800000004D30000A80F0000 |
    | TABH+ 40( 8) = 10000000C1048401 |
    | store        = 0xE078CC51 |
    | ext1         = 0xC827D051 |
    | shmId        = 0     (0x00000000) |
    | id           = 90    (0x5A000000) |
    | label        = 894   (0x7E030000) |
    | fill         = 1     (0x01000000) |
    | leng         = 879   (0x6F030000) |
    | loop         = 72    (0x48000000) |
    | xtyp         = TYPE#000061 |
    | occu         = 16    (0x10000000) |
    | access       = 1     (ItAccessStandard) |
    | idxKind      = 0     (ItIndexNone) |
    | uniKind      = 2     (ItUniqueNon) |
    | keyKind      = 1     (default) |
    | cmpMode      = 2     (cmpSingleMcmpR) |
    | occu0        = 0 |
    | groupCntl    = 0 |
    | rfc          = 0 |
    | unShareable  = 0 |
    | mightBeShared = 1 |
    | sharedWithShmTab = 0 |
    | isShmLockId  = 0 |
    | gcKind       = 0 |
    | isUsed       = 1 |
    | isCtfyAble   = 1 |
    | >>>>> Shareable Table Header Data <<<<< |
    | tabi         = 0xD81DD151 |
    | pgHook       = 0x00000000 |
    | idxPtr       = 0x00000000 |
    | shmTabhSet   = 0x00000000 |
    | id           = 713   (0xC9020000) |
    | refCount     = 1     (0x01000000) |
    | tstRefCount  = 0     (0x00000000) |
    | lineAdmin    = 16    (0x10000000) |
    | lineAlloc    = 16    (0x10000000) |
    | shmVersId    = 0     (0x00000000) |
    | shmRefCount  = 2     (0x02000000) |
    | >>>>> 1st level extension part <<<<< |
    | regHook      = 0xB8FDCF51 |
    | collHook     = 0x00000000 |
    | ext2         = 0x00000000 |
    | >>>>> 2nd level extension part <<<<< |
    | tabhBack     = Not allocated |
    | delta_head   = Not allocated |
    | pb_func      = Not allocated |
    | pb_handle    = Not allocated |
    | %_DUMMY$$ |
    |  |
    | 2222 |
    | 0000 |
    | <SIGNATURE> |
    | INTFII_BBPX_TRADING_PARTNER_SUS_INMETHEXECUTE_ASYNCHRONOUS          INPUT |
    | 4454445445555544444554554455555544445445445545455444544455222222222244555222222222222222222222 |
    | 9E4699F2208F42149E7F0124E52F353F9ED5485853545F139E382FEF5300000000009E054000000000000000000000 |
    | CL_WS_MD_FACTORY=>PROFILE_STATELESS_BASIC_AUTH |
    | ??? |
    | ?????? |
    | ?????? |
    | <SIGNATURE>-DECL |
    | 0 |
    | 3 |
    | 0 |
    | SPROX_CONST_DIR_IMPORTING |
    | 0 |
    | 3 |
    | 0 |
    | SYST-REPID |
    | CL_PROXY_INBOUND_ADAPTER======CP |
    | 4455545554444544544455453333334522222222 |
    | 3CF02F89F9E2F5E4F1410452DDDDDD3000000000 |
    | SPROX_CONST_DIR_EXPORTING |
    | 1 |
    | 3 |
    | 1 |
    | SPROX_CONST_DIR_CHANGING |
    | 2 |
    | 3 |
    | 2 |
    | CL_WB_REQUEST=>WN_SAME_WINDOW |
    | ??? |
    | ?????? |
    | ?????? |
    | LR_DATA_REF |
    | 0.0.0.0.0.0.0.1.  |
    | 6000A000 |
    | C0003000 |
    | <SIGNATURE>-TYPENAME |
    | BBPX_TRADING_PARTNER_SUS |
    | 445555544444554554455555222222 |
    | 2208F42149E7F0124E52F353000000 |
    | SY-XPROG |
    | SAPMSSY1 |
    | 5454555322222222222222222222222222222222 |
    | 310D339100000000000000000000000000000000 |
    | LV_ABAP_PARAM-VALUE |
    | 0.0.0.0.0.0.0.1.  |
    | 6000A000 |
    | C0003000 |
    | ME->ABAP_PARAMS |
    | Table IT_895[1x40] |
    | DATA=ABAP_PARAMS
    Table reference: 91
    TABH+  0(20) = 2003D05100000000000000005B0000007F030000
    TABH+ 20(20) = 0100000028000000FFFFFFFF04D3000058070000
    TABH+ 40( 8) = 10000000A4258001
    store        = 0x2003D051
    ext1         = 0x00000000
    shmId        = 0     (0x00000000)
    id           = 91    (0x5B000000)
    label        = 895   (0x7F030000)
    fill         = 1     (0x01000000)
    leng         = 40    (0x28000000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000023
    occu         = 16    (0x10000000)
    access       = 4     (ItAccessHashed)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 1     (ItUnique)
    keyKind      = 3     (user defined)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x9000D051
    pgHook       = 0x00000000
    idxPtr       = 0x6003D051
    shmTabhSet   = 0x00000000
    id           = 714   (0xCA020000)
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 16    (0x10000000)
    lineAlloc    = 16    (0x10000000)
    shmVersId    = 0     (0x00000000)
    shmRefCount  = 1     (0x01000000)
    >>>>> 1st level extension part <<<<<
    regHook      = Not allocated
    collHook     = Not allocated
    ext2         = Not allocated
    >>>>> 2nd level extension part <<<<<
    tabhBack     = Not allocated
    delta_head   = Not allocated
    pb_func      = Not allocated
    pb_handle    = Not allocated
    LV_ABAP_PARAM
    INPUT                          #l###£###
    445552222222222222222222222222206000A000
    9E054000000000000000000000000000C0003000
    SY-REPID
    CL_PROXY_INBOUND_ADAPTER======CP
    4455545554444544544455453333334522222222
    3CF02F89F9E2F5E4F1410452DDDDDD3000000000
    SY
    ############################################################################o#################
    0000000000000000000000000000000000000000000000000000000000000000000000000000600000000000000000
    0000000010001000000000000000000000000000100010001000000010000000000000000000F30000000000000000
    <SIGNATURE>-PARAM
    INPUT
    445552222222222222222222222222
    9E0540000000000000000000000000
    SCREEN
    TAB_CONTROL_TAB4
    5445444554455443222222222222222222222222222222222222222222222222222222222222222222222222222222
    412F3FE42FCF4124000000000000000000000000000000000000000000000000000000000000000000000000000000
    No.       8 Ty.          METHOD
    Name  CL_PROXY_INBOUND_ADAPTER=>IF_PROXY_INBOUND_ADAPTER~SET_METHOD
    INTERFACE
    II_BBPX_TRADING_PARTNER_SUS_IN
    445445555544444554554455555544
    99F2208F42149E7F0124E52F353F9E
    METHOD
    EXECUTE_ASYNCHRONOUS
    454455454554445444552222222222
    5853545F139E382FEF530000000000
    REQUEST_PART
    |
    | F0000000 |
    | F0000000 |
    | LR_REGISTRY |
    |
    E0001000
    2000D100
    ME
    |
    | E0001000 |
    | 90006100 |
    | No.       7 Ty.          METHOD |
    | Name  CL_PROXY_ADAPTER_TEST=>INBOUND_TEST |
    | INTERFACE |
    | II_BBPX_TRADING_PARTNER_SUS_IN |
    | 445445555544444554554455555544 |
    | 99F2208F42149E7F0124E52F353F9E |
    | METHOD |
    | EXECUTE_ASYNCHRONOUS |
    | 454455454554445444552222222222 |
    | 5853545F139E382FEF530000000000 |
    | RUNTIME |
    | RUNTIME_TEST |
    | 554544455455 |
    | 25E49D5F4534 |
    | REQUEST_DATA |
    | <n0:SupplierPortalTradingPartner xmlns:n0="http://sap.com/xi/SRM/SupplierEnablement" xmlns:prx |
    | 3633577766675677665766666567766727666736332677732276726662762554257776667466666666722766673777 |
    | CE0A3500C9520F241C42149E70124E5208DCE3AE0D28440AFF310E3FDF89F32DF3500C9525E12C5D5E4208DCE3A028 |
    | DONT_CATCH_APPL_FAULT |
    |  |
    | 2 |
    | 0 |
    | RESPONSE_DATA |
    |  |
    | ERROR_DATA |
    |  |
    | EXCEPTION_CLASS_NAME |
    |  |
    | RUNTIME_SERIALIZE |
    | 0 |
    | 0000 |
    | 0000 |
    | RUNTIME_DESERIALIZE |
    | 0 |
    | 0000 |
    | 0000 |
    | RUNTIME_EXECUTE |
    | 0 |
    | 0000 |
    | 0000 |
    | INBOUND_ADAPTER |
    |
    E0001000
    90006100
    LR_PAYLOAD_PROTOCOL
    |
    | E0001000 |
    | 4000B100 |
    | %_FSREG_001 |
    | ??? |
    | ?????? |
    | ?????? |
    | LR_REQUEST_PAYLOAD |
    |
    E0001000
    3000C100
    %_DUMMY$$
    2222
    0000
    %_SPACE
    2
    0
    SYST
    ############################################################################o#################
    0000000000000000000000000000000000000000000000000000000000000000000000000000600000000000000000
    0000000010001000000000000000000000000000100010001000000010000000000000000000F30000000000000000
    SYST-REPID
    CL_PROXY_ADAPTER_TEST=========CP
    4455545554445545554553333333334522222222
    3CF02F89F1410452F4534DDDDDDDDD3000000000
    LR_REQUEST_PART
    F0000000
    F0000000
    LV_RUNTIME_0
    0
    0000
    0000
    SY-REPID
    CL_PROXY_ADAPTER_TEST=========CP
    4455545554445545554553333333334522222222
    3CF02F89F1410452F4534DDDDDDDDD3000000000
    SY-XPROG
    SAPMSSY1
    5454555322222222222222222222222222222222
    310D339100000000000000000000000000000000
    LR_READER
    F0000000
    F0000000
    No.       6 Ty.          METHOD
    Name  LCL_SI_TEST=>IF_PROXY_SI_TEST~EXECUTE
    REQUEST
    <n0:SupplierPortalTradingPartner xmlns:n0="http://sap.com/xi/SRM/SupplierEnablement" xmlns:prx
    3633577766675677665766666567766727666736332677732276726662762554257776667466666666722766673777
    CE0A3500C9520F241C42149E70124E5208DCE3AE0D28440AFF310E3FDF89F32DF3500C9525E12C5D5E4208DCE3A028
    RESPONSE
    CALL_FAILED
    2
    0
    RUNTIME_SERIALIZE
    0
    0000
    0000
    RUNTIME_DESERIALIZE
    0
    0000
    0000
    RUNTIME_EXECUTE
    0
    0000
    0000
    %_DUMMY$$
    2222
    0000
    SCREEN
    TAB_CONTROL_TAB4
    5445444554455443222222222222222222222222222222222222222222222222222222222222222222222222222222
    412F3FE42FCF4124000000000000000000000000000000000000000000000000000000000000000000000000000000
    SY
    ############################################################################o#################
    0000000000000000000000000000000000000000000000000000000000000000000000000000600000000000000000
    0000000010001000000000000000000000000000100010001000000010000000000000000000F30000000000000000
    ME->INTERFACE
    II_BBPX_TRADING_PARTNER_SUS_IN
    445445555544444554554455555544
    99F2208F42149E7F0124E52F353F9E
    ME->METHOD
    EXECUTE_ASYNCHRONOUS
    454455454554445444552222222222
    5853545F139E382FEF530000000000
    ME->NO_CATCH
    2
    0
    LV_ERROR_DATA
    ME->EXCEPTION_CLASS_NAME
    %_VIASELSCR
    0
    4
    RSJOBINFO
    00000000000000                                  ####
    222222222222222222222222222222223333333333333322222222222222222222222222222222220000
    000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    %_PRINT
    000                                                                                0 ##
    2222333222222222222222222222222222222222222222222222222222222222222222222222222222222222223200
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    LR_APPL_FAULT
    |
    | F0000000 |
    | F0000000 |
    | %_SPACE |
    |  |
    | 2 |
    | 0 |
    | No.       5 Ty.          FORM |
    | Name  EXEC |
    | %_DUMMY$$ |
    |  |
    | 2222 |
    | 0000 |
    | GR_REQUEST |
    |
    4000B000
    70008000
    SPACE
    2
    0
    REQUEST_DATA
    <n0:SupplierPortalTradingPartner xmlns:n0="http://sap.com/xi/SRM/SupplierEnablement" xmlns:prx
    3633577766675677665766666567766727666736332677732276726662762554257776667466666666722766673777
    CE0A3500C9520F241C42149E70124E5208DCE3AE0D28440AFF310E3FDF89F32DF3500C9525E12C5D5E4208DCE3A028
    GR_CALL_FAILED
    2
    0
    RESPONSE_DATA
    LV_RUNTIME_SERIALIZE
    0
    0000
    0000
    LV_RUNTIME_DESERIALIZE
    0
    0000
    0000
    LV_RUNTIME_EXECUTE
    0
    0000
    0000
    CL_GUI_CONTROL=>LIFETIME_DEFAULT
    0
    0000
    0000
    SYST-REPID
    SAPLSPRX_SI_TEST
    5454555555455455222222222222222222222222
    310C3028F39F4534000000000000000000000000
    SCREEN
    TAB_CONTROL_TAB4
    5445444554455443222222222222222222222222222222222222222222222222222222222222222222222222222222
    412F3FE42FCF4124000000000000000000000000000000000000000000000000000000000000000000000000000000
    No.       4 Ty.          FORM
    Name  USER_COMMAND_0500
    SY-REPID
    SAPLSPRX_SI_TEST
    5454555555455455222222222222222222222222
    310C3028F39F4534000000000000000000000000
    LV_OKCODE
    EXEC
    4544222222222222222222222222222222222222222222222222222222222222222222
    5853000000000000000000000000000000000000000000000000000000000000000000
    GV_SAMPLE_RESPONSE_PAYLOAD
    %_SPACE
    2
    0
    G_TAB_CONTROL-PRESSED_TAB
    REQUEST
    5455455222222222222222222222222222222222222222222222222222222222222222
    2515534000000000000000000000000000000000000000000000000000000000000000
    GR_RESPONSE
    |
    | 5000A000 |
    | D0002000 |
    | %_VIASELSCR |
    | # |
    | 0 |
    | 4 |
    | SY-XPROG |
    | SAPMSSY1 |
    | 5454555322222222222222222222222222222222 |
    | 310D339100000000000000000000000000000000 |
    | No.       3 Ty.          MODULE (PAI) |
    | Name  USER_COMMAND_0500 |
    | %_PRINT |
    | 000                                                                                0 ## |
    | 2222333222222222222222222222222222222222222222222222222222222222222222222222222222222222223200 |
    | 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
    | No.       2 Ty.          FUNCTION |
    | Name  SPRX_SI_TEST |
    | SI_TEST |
    |
    F0000000
    C0003000
    G_TAB_CONTROL
    0600SAPLSPRX_SI_TEST                        REQUEST
    3333545455555545545522222222222222222222222254554552222222222222222222222222222222222222222222
    0600310C3028F39F453400000000000000000000000025155340000000000000000000000000000000000000000000
    GR_SI_TEST
    |
    | F0000000 |
    | C0003000 |
    | GV_CANCELED |
    |  |
    | 2 |
    | 0 |
    | ABAP_FALSE |
    |  |
    | 2 |
    | 0 |
    | SY-XFORM |
    | XAB_READ |
    | 544554442222222222222222222222 |
    | 812F25140000000000000000000000 |
    | GR_CONTAINER |
    |
    4000B000
    90006000
    GR_REFERENCE
    |
    | 80007000 |
    | 0000F000 |
    | GR_DIFF |
    |
    80007000
    3000C000
    No.       1 Ty.          EVENT
    Name  START-OF-SELECTION
    SY-SUBRC
    0
    0000
    0000
    SY-REPID
    SPROX_SERVICE_INTERFACE_TEST_I
    5554555455444544545444455455542222222222
    302F8F3526935F9E4526135F4534F90000000000
    SY-MSGID
    22222222222222222222
    00000000000000000000
    SPACE
    2
    0
    SY-MSGNO
    000
    333
    000
    %_P_INTF_%_APP_%
    Interface Name
    467676666246662222222222222222
    9E45261350E1D50000000000000000
    SY-MSGV1
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    SY-MSGV2
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    SY-MSGV3
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    SY-MSGV4
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    LR_SI_TEST
    F0000000
    C0003000
    R3NAME
    II_BBPX_TRADING_PARTNER_SUS_IN
    445445555544444554554455555544
    99F2208F42149E7F0124E52F353F9E
    METHOD
    222222222222222222222222222222
    000000000000000000000000000000
    %_P_METH_%_APP_%
    Method Name
    467666246662222222222222222222
    D548F40E1D50000000000000000000
    Internal notes
    The termination was triggered in function "method_call_iref"
    of the SAP kernel, in line 2207 of the module
    "//bas/700_REL/src/krn/runt/abmethod.c#10".
    The internal operation just processed is "METH".
    Internal mode was started at 20081213173634.
    Active Calls in SAP Kernel
    Lines of C Stack in Kernel (Structure Differs on Each Platform)
    SAP (R) - R/3(TM) Callstack, Version 1.0
    Copyright (C) SAP AG. All rights reserved.
    Callstack without Exception:
    App       : disp+work.EXE (pid=4716)
    When      : 12/13/2008 17:36:42.685
    Threads   : 2
    Computer Name       : SRMSUS
    User Name           : SAPServiceSRD
    Number of Processors: 4
    Processor Type: x86 Family 15 Model 2 Stepping 7
    Windows Version     : 5.2 Current Build: 3790
    State Dump for Thread Id 1288
    eax=000fb648 ebx=000003a8 ecx=00000038 edx=00000000 esi=000003a8 edi=00000000
    eip=7c8285ec esp=0465dc9c ebp=0465dd0c iopl=0         nv up ei ng nz ac po cy
    cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00200297
    function : KiFastSystemCallRet
    7c8285ec c3               ret
    7c8285ed 8da42400000000   lea     esp,[esp]              ss:0465dc9c=7c827d0b
    7c8285f4 8d642400         lea     esp,[esp]              ss:2266ccaf=????????
    FramePtr ReturnAd Param#1  Param#2  Param#3  Param#4  Function Name
    0465dd0c 77e61c8d 000003a8 0001d4c0 00000000 0465dd44 ntdll!KiFastSystemCallRet
    0465dd20 01066cf4 000003a8 0001d4c0 00000001 7c3ab718 kernel32!WaitForSingleObject
    0465dd44 00585f0e 00585f47 7c3ab718 7c3ab718 7c3ab718 disp+work!NTDebugProcess
    0465dd48 00585f47 7c3ab718 7c3ab718 7c3ab718 01ca73bc disp+work!NTStack
    0465dd64 00585f7b 7c3ab718 00000000 008acf08 7c3ab718 disp+work!CTrcStack2
    0465dd70 008acf08 7c3ab718 00000000 32305f59 39303030 disp+work!CTrcStack
    0465dd8c 008b02dd 51cf3fd0 00008002 00000000 51b20548 disp+work!rabax_CStackSave [abrabax.c (7125)
    0465e220 006d1f09 012ca01c 012c9ffc 0000089f 01d0bfc0 disp+work!ab_rabax
    0465e250 006e2868 00000003 51c99e30 00000000 0465e2b8 disp+work!method_call_iref [abmethod.c (2207
    0465e2b8 0081cecf 00000000 51c99e30 0465e308 51c9af4d disp+work!ab_extri
    0465e2cc 0088eecd 00000000 51c9ad56 005c5927 51c9a814 disp+work!ab_xevent
    0465e2d8 005c5927 51c9a814 00000022 51c9ad56 00000000 disp+work!ab_dstep
    0465e380 005c8c7f 51c99e30 51c99e30 0465fd4c 00000000 disp+work!dynpmcal
    0465e394 005c82a0 51c99e30 51c99e30 00000003 0465fd4c disp+work!dynppai0
    0465e3b0 0059a493 51c99e30 00000003 00000001 00000001 disp+work!dynprctl
    0465fdc0 00494f08 00000002 004a167e 00000002 00000000 disp+work!dynpen00
    0465fdc8 004a167e 00000002 00000000 00000003 00000002 disp+work!Thdynpen00
    0465fee4 004a1bfb 002463f8 00000001 00000000 01bca464 disp+work!TskhLoop
    0465ff00 004237f9 00000000 00000000 7ffde000 0465ff60 disp+work!ThStart
    0465ff14 0040108a 00000003 002463f8 00000001 00000000 disp+work!DpMain
    0465ff60 0122a2c0 00000003 002463f8 00242ca0 01b69000 disp+work!nlsui_main
    0465ffc0 77e6f23b 00000000 00000000 7ffde000 00000000 disp+work!mainCRTStartup
    0465fff0 00000000 0122a17d 00000000 00000000 00000000 kernel32!ProcessIdToSessionId
    State Dump for Thread Id 1340
    eax=00000001 ebx=00000103 ecx=7c829f59 edx=004b0000 esi=00000000 edi=00000000
    eip=7c8285ec esp=06aafec0 ebp=06aaff04 iopl=0         nv up ei pl zr na po nc
    cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000246
    function : KiFastSystemCallRet
    7c8285ec c3               ret
    7c8285ed 8da42400000000   lea     esp,[esp]              ss:06aafec0=7c8270fb
    7c8285f4 8d642400         lea     esp,[esp]              ss:24abeed3=????????
    FramePtr ReturnAd Param#1  Param#2  Param#3  Param#4  Function Name
    06aaff04 0116fba0 00000694 00000000 00000000 002481d8 ntdll!KiFastSystemCallRet
    06aaff84 7c36b381 00000000 00000000 00000000 00248140 disp+work!SigIMsgFunc
    06aaffb8 77e64829 00248140 00000000 00000000 00248140 MSVCR71!endthreadex
    06aaffec 00000000 7c36b312 00248140 00000000 00000000 kernel32!GetModuleHandleA
    List of ABAP programs affected

    Dear Ashok,
    Please follow the below steps then it should work.
    1. Call transaction BBP_SUS_BP_ADM to start supplier replication
    monitoring.
    2. If the e-mail address is incorrect, choose Delete. Change the e-mail
    address in the procurement system and replicate the supplier master data again.
    3. If the supplier master data was not created via supplier registration, select New Business Partner. Change the e-mail address in the
    procurement system and replicate the supplier again.
    Still if you are unable to replicate the vendors then let us know.
    Thanks
    Ravi

  • Automitic source of supply assignment in backend system for SRM

    Hello Experts,
    I am facing one issue regarding source of supply for SRM purchase Requisitions in backend ECC system.
    When we create a shopping cart in SRM 5.0, a purchase requisition is created in backend and has source of supply assigned to it.
    I donu2019t want to assign source of supply to purchase requisitions created for SRM.
    Can you please suggest how to achieve this?
    Also I think, SRM is internally using BAPI u201CBAPI_REQUISITION_CREATEu201D from backend ECC system for creation of requisition. This BAPI has an importing parameter u2018AUTOMATIC_SOURCEu2019, and if we pass space to this parameter, it creates requisition without assigning source of supply.
    If this is correct, then can I use any BADI or customization in SRM to set the value of this parameter as space when SRM calls this BAPI?
    Thanks in Advance.
    Thanks and Regards,
    Sanjay

    SPRO--> SRM > SRM server> cross application basic settings --> Define objects in backend system (PR,RS,PO)
    waht is the settings you maintained for your product category / purchase group - external procurement .
    the above setting determines your follow on documents in the backend systems.
    as discuused in the thread are you using any BADI ?
    Unable to create PO in backend system for a text material in Shopping cart
    peter offers how to debug to ..in the above link.
    br
    muthu

Maybe you are looking for