Value SAP

Hi,
What is the Value SAP and ASAP methodology? the differenemce between these two?
REgards.

Hi,
ASAP or Accelerated SAP and Value SAP are both project phases for implementation. ASAP has 5 phases - Project preparation, business blueprint, realization, final prep. golive and support. Each face has a deliverable.
These phases have been restructured in Value SAP into three phases - Discovery and evolution, Implementation and Operations & continous Improvement.
Link for Value SAP -
[http://help.sap.com/printdocu/core/Print46c/en/data/pdf/SVASAP/SVASAP.pdf]
Hope this helps
Thanks and Regards,
Anit

Similar Messages

  • Installation of Value SAP

    Hi all,
    I need to install Value SAP (VSAP). I tried but there is some error.
    Actually for the discovery phase, the diagram explorer is installing fine. But for the subsequent steps like implementation and continuous inprovement, when i tried to install diagram explorer it says, " <i>Setup has detected a diagram explorer</i>".
    Q1. <b>Should i need to install only one diagram explorer for all the three phases?</b>
    Q2. <b>Or shud i need to install 3 diagram explorer in different paths. If yes, how?</b>
    Please help.... Its very urgent.....
    Thanks,
    Architha.

    hi,
    try to set the SAP_REGISTRY_PATH Environment Variable manually.
    This Note could help: 530297
    regards
    Tobias

  • Calculate two values (SAP HRFORMS)

    Dear All,
    I need held calculating two values within HRFOMS.
    I would like to have a screenfield with the value of the current page Therefore i got a global variable G_total_pagecount and i have the current page xfa.layout.page(this)
    I tried  the following
    data.#pageSet[0].Startseite.Titel_und_Anschrift.Allgemeine_Daten.Org_Daten.Seite_global::r eady:layout
    $.rawValue = $record.G_TOTAL_PAGECOUNT + xfa.layout.page(this)
    and received no value
    or
    var page = parseInt(xfa.layout.page(this), 10); // , 10 erzwingt die Umwandlung als dezimalzahl
    var global = parseInt(xfa.record.G_TOTAL_PAGECOUNT, 10)
    var total = page + global:
    this.rawValue = total.rawValue;
    But both did not work
    I would be happy to get any new idea
    Angela

    Hi Paul,
    first of all many thanks for your help. I normally do only Abap programming, bur unfortunatly I ended up with this HRFORMS Payslip. I have no idea how to decide to choose Formcalc or javascript. I only tried some small pieces which i got from the online help.
    I did try the following
    ----- data.#pageSet[0].Startseite.Titel_und_Anschrift.Allgemeine_Daten.Org_Daten.Seitenzahl::ready:layout - (FormCalc, Client)
    $.rawValue
    = $record.G_TOTAL_PAGECOUNT + xfa.layout.page($)
    => id did not get a value in my field
    than I tried
    ----- data.#pageSet[0].Startseite.Titel_und_Anschrift.Allgemeine_Daten.Org_Daten.Seitenzahl::calculate: - (JavaScript, Server)
     var  1 = parseInt(xfa.layout.page(this), 10); // , 10 erzwingt die Umwandlung als dezimalzahl
    var  2 = parseInt(xfa.record.G_TOTAL_PAGECOUNT, 10)this.rawValue
    = 1 + 2;
    => still no value
    Last I tried
    ----- data.#pageSet[0].Startseite.Titel_und_Anschrift.Allgemeine_Daten.Org_Daten.Seitenzahl::ready:layout - (JavaScript, Client)
     var  1 = parseInt(xfa.layout.page(this), 10); // , 10 erzwingt die Umwandlung als dezimalzahl
    var  2 = parseInt(xfa.record.G_TOTAL_PAGECOUNT, 10)this.rawValue
    = 1 + 2;
    Still no succsess
    As I am working within HRFORM i only get limited Error Messages or warnings and for everything i tried i did not get a warning at all.
    It would be really nice if you could tell me what i did wrong
    Thanks in advance
    Angela

  • VALUE SAP DVD number?

    Hi all,
    where can get this DVD download....
    searched in Service market place downloads but its not availabale....
    will you please help us.....
    cheers,
    vasanth.

    You can download from service marketplace (service.sap.com/swdc). Navigate to the path show below
    Installations and Upgrades-> Entry by application group-> SAP NetWeaver-> SAP MDM-> SAP MDM 5.5
    regards
    Suman

  • Publishing issue with BOE XI 3.1 and SAP IK

    Hi There,
    this issue has been posted a few times before and I see other people are running into it as well. Nonetheless I have not found a satisfying answer in the Forum.
    I have the problem that I can only publish a Crystal Report based on SAP BI if the publishing role is an Admin in BOE. that is not how it is supposed to work.
    I followed all the guidelines and required settings and as soon as the publisher is no administrator I get an error. Publishing to BI works fine.
    The error I get is:
    An error occurred while saving and/or publishing. The return code 1 was returned from the server. An error occurred when synchronizing folder hierarchy for role:......
    Here is the publishing log:
    essage
    [Thu Nov 20 10:06:33 2008]     2664     1688     Entering CPubReqPublishReport::Process(1)
    [Thu Nov 20 10:06:33 2008]     2664     1688     Entering CPubBWConnector::GetQueryLocation()
    [Thu Nov 20 10:06:33 2008]     2664     1688       SAP_LANGUAGE set to EN (got from rfc handle)
    [Thu Nov 20 10:06:33 2008]     2664     1688     SAP Publisher BW Binding: 1 roles returned. Deduced active system id to be 00001 from the first row [role: Y:BI_PROG_MGR]
    [Thu Nov 20 10:06:33 2008]     2664     1688     System 00001: Name: base_folder Value /SAP/2.0/
    [Thu Nov 20 10:06:33 2008]     2664     1688     System 00001: Name: ce_aps_nam Value cepvsabob81:6400
    [Thu Nov 20 10:06:33 2008]     2664     1688     System 00001: Name: ce_lang_list Value D E
    [Thu Nov 20 10:06:33 2008]     2664     1688     System 00001: Name: ce_path_pr Value SAP
    [Thu Nov 20 10:06:33 2008]     2664     1688     System 00001: Name: ce_protcl Value http
    [Thu Nov 20 10:06:33 2008]     2664     1688     System 00001: Name: ce_server Value cepvsabob81.gov.edmonton.ab.gov:8080
    [Thu Nov 20 10:06:33 2008]     2664     1688     System 00001: Name: ce_viewer Value reportView.do
    [Thu Nov 20 10:06:33 2008]     2664     1688     System 00001: Name: folder_policy Value FCT
    [Thu Nov 20 10:06:33 2008]     2664     1688     System 00001: Name: report_policy Value FCT
    [Thu Nov 20 10:06:33 2008]     2664     1688     Running job synchronously
    [Thu Nov 20 10:06:33 2008]     2664     1688     Entering job processor CPubJobGetRoleMetaData(Y:BI_PROG_MGR)
    [Thu Nov 20 10:06:33 2008]     2664     1688     Entering CopyRfcHandle(1)
    [Thu Nov 20 10:06:33 2008]     2664     1688     Starting up callback server at 162.106.114.62 sapgw16 with prog-id SEGIDDC806AA2A01688
    [Thu Nov 20 10:06:33 2008]     2664     1688     GetRfcHandle() returned with handle 2
    [Thu Nov 20 10:06:33 2008]     2664     1688     Leaving job processor CPubJobGetRoleMetaData(Y:BI_PROG_MGR)
    [Thu Nov 20 10:06:33 2008]     2664     1688     Logging on to Crystal Enterprise
    [Thu Nov 20 10:06:35 2008]     2664     1688     Logged on to CMS "cepvsabob81:6400" as user "BIX~001/DUMMY" with id 1815
    [Thu Nov 20 10:06:35 2008]     2664     1688     Generating Enterprise token "cepvsabob81.COE.ADS:6400@1897JkHE9ilGJ2Hgcinp1895JceHlHlYrNTzUBPQ" for use with repository linked reports.
    [Thu Nov 20 10:06:35 2008]     2664     1688     Worker thread created. Placing in active queue.
    [Thu Nov 20 10:06:35 2008]     2664     1688     Base folder hierarchy: /SAP/2.0/BIXCLNT001
    [Thu Nov 20 10:06:35 2008]     2664     1688     FindFolder Query: SELECT SI_ID, SI_PATH FROM CI_INFOOBJECTS WHERE SI_NAME='BIXCLNT001' AND SI_PROGID='CrystalEnterprise.Folder'
    [Thu Nov 20 10:06:35 2008]     2664     6784     Entering job processor CPubJobCompositeReport
    [Thu Nov 20 10:06:35 2008]     2664     6784     Running job synchronously
    [Thu Nov 20 10:06:35 2008]     2664     6784     Entering job processor CPubJobDownloadReport(4BW89NXFO63ORDK4YMDSU0GN2)
    [Thu Nov 20 10:06:35 2008]     2664     6784     Reused connection 2
    [Thu Nov 20 10:06:36 2008]     2664     1688     FindFolder returned 1 items from query SELECT SI_ID, SI_PATH FROM CI_INFOOBJECTS WHERE SI_NAME='BIXCLNT001' AND SI_PROGID='CrystalEnterprise.Folder'
    [Thu Nov 20 10:06:36 2008]     2664     1688     Base folder id is 1465
    [Thu Nov 20 10:06:36 2008]     2664     1688     Worker thread created. Placing in active queue.
    [Thu Nov 20 10:06:36 2008]     2664     1688     CPubReqPublishReport::force_mode string()
    [Thu Nov 20 10:06:36 2008]     2664     6784     Downloaded report 4BW89NXFO63ORDK4YMDSU0GN2 with master langugage E in the following languages: D E
    [Thu Nov 20 10:06:36 2008]     2664     1688     CPubReqPublishReport::force_mode_bool(false)
    [Thu Nov 20 10:06:36 2008]     2664     6784     Adjusted language list for report 4BW89NXFO63ORDK4YMDSU0GN2 is "E"
    [Thu Nov 20 10:06:36 2008]     2664     1688     About to start publishing reports to CE. Waiting for folders and report metadata.
    [Thu Nov 20 10:06:36 2008]     2664     6784     Leaving job processor CPubJobDownloadReport(4BW89NXFO63ORDK4YMDSU0GN2)
    [Thu Nov 20 10:06:36 2008]     2664     6784     Running job synchronously
    [Thu Nov 20 10:06:36 2008]     2664     6784     Entering job processor CPubJobProcessReport
    [Thu Nov 20 10:06:36 2008]     2664     6784     Reused connection 2
    [Thu Nov 20 10:06:36 2008]     2664     2448     Entering job processor CPubJobCEFolders(Y:BI_PROG_MGR)
    [Thu Nov 20 10:06:36 2008]     2664     2448     CPubLocFolderHierarchy::ParseRoleFolderInfo:l_sText:[Projektcontroller]
    [Thu Nov 20 10:06:36 2008]     2664     2448     CPubLocFolderHierarchy::ParseRoleFolderInfo:l_sText:[Program Manager]
    [Thu Nov 20 10:06:36 2008]     2664     2448     CPubLocFolderHierarchy::ParseRoleFolderInfo:l_sText:[BOBJ_Test_1]
    [Thu Nov 20 10:06:36 2008]     2664     2448     FindObjects query: SELECT SI_NAME, SI_LOC_NAMES, SI_LOC_ORIGINAL_LOCALE FROM CI_INFOOBJECTS WHERE SI_PROGID='CrystalEnterprise.Folder' AND SI_PARENT_FOLDER='1465' AND SI_SAP_FOLDER_ID='Y:BI_PROG_MGR                 0000000000'
    [Thu Nov 20 10:06:36 2008]     2664     2448     FindObjects returned 1 items from query SELECT SI_NAME, SI_LOC_NAMES, SI_LOC_ORIGINAL_LOCALE FROM CI_INFOOBJECTS WHERE SI_PROGID='CrystalEnterprise.Folder' AND SI_PARENT_FOLDER='1465' AND SI_SAP_FOLDER_ID='Y:BI_PROG_MGR                 0000000000'
    [Thu Nov 20 10:06:36 2008]     2664     2448     FindObjects query: SELECT SI_PATH FROM CI_INFOOBJECTS WHERE SI_ID='1808' AND SI_PROGID='CrystalEnterprise.Folder'
    [Thu Nov 20 10:06:36 2008]     2664     2448     FindObjects returned 1 items from query SELECT SI_PATH FROM CI_INFOOBJECTS WHERE SI_ID='1808' AND SI_PROGID='CrystalEnterprise.Folder'
    [Thu Nov 20 10:06:36 2008]     2664     2448     FindObjects query: SELECT SI_ID FROM CI_SYSTEMOBJECTS WHERE SI_NAME='BIX~001@Y:BI_PROG_MGR'
    [Thu Nov 20 10:06:36 2008]     2664     2448     FindObjects returned 0 items from query SELECT SI_ID FROM CI_SYSTEMOBJECTS WHERE SI_NAME='BIX~001@Y:BI_PROG_MGR'
    [Thu Nov 20 10:06:36 2008]     2664     2448     ERROR: ..\..\src\ce_folder_hierarchy.cpp [328]: E_NOINTERFACE failed with return code l_hr = -2147467262
    [Thu Nov 20 10:06:36 2008]     2664     2448     COM Exception caught in CCEFolderHierarchy::RelateFolderToUserGroup. HRESULT = -2147467262
    [Thu Nov 20 10:06:36 2008]     2664     2448     ERROR: .\ce_folders.cpp [226]: m_objBaseHierarchy.RelateFolderToUserGroup(l_sFullUserGroupName, l_nRoleRootFolderId) failed with return code l_hr = -2147467262
    [Thu Nov 20 10:06:36 2008]     2664     2448     Leaving job processor CPubJobCEFolders(Y:BI_PROG_MGR)
    [Thu Nov 20 10:06:36 2008]     2664     1688     error happened when synchronizing role folder
    [Thu Nov 20 10:06:36 2008]     2664     1688     Leaving CPubReqPublishReport::Process(1)
    [Thu Nov 20 10:06:36 2008]     2664     1688     Dispatch returned with code 0 and message [See RFC trace file or SAP system log for more details]
    [Thu Nov 20 10:06:36 2008]     2664     6784     Content marker: 0
    If someone ran into this issue and fixed it could you please give me your steps so I can check with what I did?
    Thanks,
    Stephan

    Hi,
    - the user that is supposed to publish a report needs to be part of a role that has been imported
    - that role needs to have the rights to view, edit, add, modify object as part of the role folder (or higher in the folder structure like the SAP system ID Folder).
      detailed list of rights :
         Add objects to the folder that the user owns
         Add objects to the folder
         Copy objects to another folder that the user owns
         Copy objects to another folder
         Delete objects that the user owns
         Delete objects
         Edit objects
         Edit objects that the user owns
         Modify the rights users have to objects
         View objects
         View objects that the user owns
    - you then need to assign a principal to the user group in BOE (CMC > Users and Groups > select the group > add principal) and assign the same rights
    - then go to the Access Levels and use the Manage > user security option and give the role the following rights :
         View objects
         View objects that the user owns
         Edit Objects
         Edit objects that the user owns
         Use Access level for security assignment
    Ingo

  • Setting initial values on structures

    I have written a middle-ware wrapper which allows me to call a SAP RFC from SQL Server stored procedures.  I am upgrading it from the DCOM to the .Net connector so I can run it on Windows 2003 Server.
    When I set a string value (SAP C type) to initial I get the error "Object reference not set to an instance of an object." raised in the proxy object.  This error does not happen for non-initial values, and also does not happen on my development workstation.  It happens if I set the string to "" or to " ". It occurs on two servers - Windows 2000 and Windows 2003.
    I can't figure out how to debug this, and can't find anything in this forum or on SAP Notes.  Has anyone else found this error?

    A clear head in the morning makes all the difference. There was no problem with the .Net Connector.
    The problem lay with SQL Server's sp_OAMethod procedure, or possibly in the .Net component's CCW.  If you pass an empty string in as an argument, your component gets a Nothing.  I therefore fixed it in the component with:
       If Value Is Nothing Then Value = ""
    Thanks,
    Derek

  • How can we Restict the Char single value Variables with , , =

    Hi Experts,
    How can we Restict the Char value Variables with <, >, <=  (without selecting Inverval or only passing single value)
    For Example
    We have a standard Query 0FIAR_C03_Q1005, in this
    New Selection
    "1 - 15 Days, Posting Date<=Key Date, Clearing Date>Key Date"
    This is restricted  with the
    Clearing(0CLEAR_DATE)
    <Clearing key date(0P_KEYD3)  It is a single value SAP Exit Varible
    PostingDate(0PSTNG_DATE)
      <= Posting keydate(0P_KEYD3)  It is a single value SAP Exit Varible
    When seeing these 0P_KEYD3, 0P_KEYD3 variables in the New selection screen they looks like  >0P_KEYD3, <=0PSTNG_DATE
    if you define any custom variables these are looks like =ZV_DATE.
    to enable < , >, <= symbols for variables what we need to do.
    In other way
    Say we created one variable ZV_DATE single value, processing type as customer exit.
    for this we populated current day,
    Now Requirement is we need to display the all the records which are <= current date,
    instead of passing low and high values, i want to restrict the calday <=ZV_DATE
    New selection
    0calday
      <=ZV_DATE
    How can we achive this, this is how the business content report having the restrictions
    Please sugget me.
    Thanks
    Chandra
    Edited by: Chandra Gandla on Jun 18, 2010 11:01 AM
    Edited by: Chandra Gandla on Jun 18, 2010 11:01 AM

    Ok,
    In the InfoObject 0calday in the query designer under the filter area, under characteristic restrictions right-click over that InfoObject (0calday).
    In the next window (select Values for [0CALDAY]  Calendar Day in the dropdown box for "Show" choose Value Ranges. Under the word "Between"  dropdown box select "Less than or equal to"
    Below that word click on the button of the dropdown box Select from list.
    In the new window select instead of History Variables and double-click on your variable ZV_DATE.
    Click on the right blue arrow to move it to the right.
    And there you go.
    Tip: It exists a SAP standard variable named 0DAT which is exactly the current date (don't need to use ZV_DATE variable).
    Diogo.

  • Webinar: How to implement secure scenarios with SAP NW PI 7.1

    SAP Intelligence Platform & NetWeaver RIG APJ Expert Call
    Dear valued SAP Experts,
    Next SAP Intelligence Platform & NetWeaver RIG Expert Call Session will take place on Tuesday, August 18.
    The SAP Intelligence Platform & NetWeaver RIG Expert Call Sessions are designed to support consultants, partners and customers  during their implementation projects. The sessions cover all different aspects of SAP NetWeaver and are aimed at
    thus provide knowledge which is not available via standard training courses. The session duration is typically 60min and includes questions and answers.
    Tuesday, August 18, 2009:
    How to implement secure scenarios with SAP NetWeaver Process Integration 7.1
    Time: 2.00 - 3.00 p.m. Singapore Time (UTC +8)
    This event will feature Makoto Sugishita with the SAP Intelligence Platform & NetWeaver Regional Implementation Group.
    Makoto provides the following abstract:
    In this session you will learn more about the core security concepts that are provided with the service-oriented architecture (SOA)
    management capabilities in SAP NetWeaver Process Integration (SAP NetWeaver PI). This session will cover main use cases and
    supported scenarios of secure SAP NetWeaver PI deployments. 
    SAP Connect Link: https://sap.emea.pgiconnect.com/I016095
    (no passcode needed)
    Dial in:
    For dial in details please register here http://www.surveymonkey.com/s.aspx?sm=EFeuZl9PxrwKOW5i5W556g_3d_3d
    Kind regards,
    Sarma Sishta
    SAP Intelligence Platform & NetWeaver RIG APJ

    hi,
    I'm making this a sticky thread till August 18 so it will have better visibility
    Regards,
    Michal Krawczyk

  • Webinar:SAP NetWeaver Process Integration u2013 Advanced Adapter Engine in PI 7

    +Please Note: This webinar is aimed at consultants, Patners and Customers in APJ Region and is scheduled at  2.00 - 3.00 p.m. Singapore Time (UTC +8)+
    Dear valued SAP Experts,
    Next SAP Intelligence Platform & NetWeaver RIG Expert Call Session will take place on Tuesday, September 1. The SAP Intelligence Platform & NetWeaver RIG Expert Call Sessions are designed to support consultants, partners and customers during their implementation projects. The sessions cover all different aspects of SAP NetWeaver and are aimed at experts, thus provide knowledge which is not available via standard training courses. The session duration is typically 60min and includes questions and answers.
    Tuesday, September 1, 2009:
    SAP NetWeaver Process Integration u2013 Advanced Adapter Engine in PI 7.1 EHP1
    Time: 2.00 - 3.00 p.m. Singapore Time (UTC +8)
    This event will feature Charu Goel with the SAP Intelligence Platform & NetWeaver Regional Implementation Group. Charu provides the following abstract:
    With PI 7.1 Enhancement pack 1, we continuously thrive to bring in advancements in AAE. In this APJ expert call, we talk about the much awaited capability of IDOC packaging along with the enhancements in JMS. You will learn about the interaction between the AAE and ABAP stack, new enhancements on the JDBC adapter and overall improvements in the technical adapters available with PI 7.1 EHP1.
    For meeting and Dial-in detail please register [here|http://www.surveymonkey.com/s.aspx?sm=qkBfQCM5FM_2f_2b4O0ihVpFRw_3d_3d]
    Thanks & Best Regards,
    Sarma Sishta

    Hi,
    This was one of the good session...
    Especially the features such as;
    -- TCP/IP connection control with JMS adapters
    -- Empty file Handling
    -- Set the various Attributes for Mail attachments via dynamic configuration (intially only subject line was possible)
    -- Message Prioritization
    -- single IDOC Ack for IDOC Packaging
    -- IDOC packaging
    -- and many more........................
    Even the future indicatioon of IDOC J2EE based adapter will provide new direction to the existion IDOC related scenarios..
    One thing that was changed in IDOC packaging is to control it via Sender Communication channel...intially we were doing it either via ECC system or with t-code "idxpw"
    Its almost in same way...but from J2EE based adapter perceptive IDOC packaging will be available with Java stack...and will no need to depend only ABAp stack for this feature.
    Thanks
    Swarup

  • How to determine the SAPS for Systems

    HI, I have the cuestion concerning to value SAPS
    I need to know the value = 600 SAPS
    value memory = ???
    value CPU   =  ????

    Hi Eli Daniel Ramones,
    You should do the sizing of the sap system that you want to install, depending of the paramteres yoy obtain a several SAP units, that will be converter for your hardware vendor as a specified machine, that you need.
    https://service.sap.com/sizing
    good luck

  • Mapping node name and value

    Hi,
    I have source strcture as
    ID
    Code
    Dept
    City
    My target structure is
    Name
    Value
    After mapping i need my target xml file to be
    <Object>
    <Name>ID</Name>
    <Value>001</Value>
    <Name>Code</Name>
    <Value>XYZ</Value>
    <Name>Dept</Name>
    <Value>SAP</Value>
    <Name>City</Name>
    <Value>NY</Value>
    </Object>
    Any input?

    let me explain my scenario more clearly...
    My source message is Idoc whose structure is as follows
    IDOC        1..1
    - E1AFKOL   1..1
       Dept
       Code
    -- E1AFKOL  0..99999
    E1AFVOL 0..99999
    E1RESBL 0..99999
          Charg
    Now my otarget strcuture is
    ObjectCollection 1..1
    -Object          0..99999
    --Field          0..99999
       Name
       Value
    Now what i want is, for each occurance of Segment E1AFVOL, Object node should get repeated and for each occurance of segment E1RESBL (child of segment E1AFVOL) 'Field' node should be repeated.
    e.g. Input is
    IDOC        1..1
    - E1AFKOL   1..1
       Dept     SAP
       Code     001 
    -- E1AFKOL  0..99999
    E1AFVOL 0..99999
    E1RESBL 0..99999
          Charg  A1
    E1RESBL 0..99999
          Charg  A2
    E1AFVOL 0..99999
    E1RESBL 0..99999
          Charg  A1
    Therefor output would be
    ObjectCollection
    -<Object>        
    --<Field>        
       Name  CHARG
       Value A1
       Name  Dept
       Value SAP
       Name  Code
       Value 001
    --</Field>
    --<Field>        
       Name  CHARG
       Value A2
       Name  Dept
       Value SAP
       Name  Code
       Value 001
    --</Field>
    -</Object>
    -<Object>        
    --<Field>        
       Name  CHARG
       Value A1
       Name  Dept
       Value SAP
       Name  Code
       Value 001
    --</Field>  
    -</Object>
    i am not sure if this can be achieved by graphical mapping.
    If not please explain me how XKST mapping would be used in this case?

  • How to validate a field of type text for similar values

    Hi,
    My requirement is to validate a field <b>Name1</b> of type Text[40] for similar values when a new record is created. So If the Name1 already exist in repository, the validation has to give warning message saying the customer with Name1 already exist.
    Regards,
    Madhu

    Hi Madhu
    To validate a particular field, when a new record comes along with the same value SAP MDM is not capable of generating warning messages, but we can have best method of Tracking at Import manager level.
    In the Import manager after successful mapping, access the MATCH RECORD tab. Go to the Default import action area there you can find Match type & Default import action. For example if you are sending same Material record which is already available in the Repository, Match type will have the value “EXACT” where as Default Import action will have “UPDATE (ALL MAPPED FIELDS or NULL FIELDS)”.
    Here I have copied various Match types as well as Default Import Actions along with the definitions, pls go thru the same and feel free to revert to me for further clarifications.
    <u><b>Default Import Action</b></u>
    <b>Skip -></b> Skip source value combinations that already
            exist.
    <b>Update(NULL Qualifiers Only) -></b>     Update just the NULL remaining qualifiers of each existing qualified lookup value.
    <b>Update (All Mapped Qualifiers)-></b> Update all the remaining qualifiers of each existing
    qualified lookup value.
    <b>Replace -></b> Replace all the remaining qualifiers of each existing qualified lookup value by first deleting them and then creating a new value combination.
    <b>Delete -></b> Delete this qualified lookup value during import Processing.
    <u><b>Match Type</b></u>
    <b>None -></b> None
    <b>Exact -> </b> Whether the match type for the destination record with the current source
    record is Exact.
    <b>Partial -></b> Whether the match type for the destination record with the current source
    record is Partial.
    <b>Conflict -></b> Whether the match type for the destination record with the current source
    record is Conflict.
    Thanks
    Alexander
    Message was edited by: Alexander Raja

  • Handling Dropdown values in Webdynpro ABAP

    Hello All,
    i have a Dropdown list in my screen which is having values
    SAP
    ABAP
    WebDynpro.
    am able to display these three values on the drop down using a method POPULATE_DROPDOWN.
    Code i have used here:
    method POPULATE_DROPDOWN .
      DATA: it_value_set_reports    TYPE TABLE OF wdr_context_attr_value,
            wa_value_set_reports    TYPE wdr_context_attr_value,
            lr_node_info_reports    TYPE REF TO if_wd_context_node_info.
        wa_value_set_reports-value = '01'.
        wa_value_set_reports-text = 'SAP'.
        APPEND wa_value_set_reports TO it_value_set_reports.
        wa_value_set_reports-value = '02'.
        wa_value_set_reports-text = 'ABAP'.
        APPEND wa_value_set_reports TO it_value_set_reports.
        wa_value_set_reports-value = '03'.
        wa_value_set_reports-text = 'WebDynpro'.
        APPEND wa_value_set_reports TO it_value_set_reports.
      APPEND INITIAL LINE TO it_value_set_reports.
      IF NOT it_value_set_reports IS  INITIAL.
        lr_node_info_reports = wd_context->get_node_info( ).
        lr_node_info_reports->set_attribute_value_set( name = 'REPORTS'
        value_set = it_value_set_reports ).
      ENDIF.
    endmethod.
    This is working fine.
    there is an action ONACTIONDISPLAY is associated with it.
    once we select a value from the dropdown the above method triggers. here i have to capture the value which is selected from the dropdown.
    Eg: Suppose if i select SAP then in the output it has to display data associated with SAP.
    Could anyone suggest how to do that step by step.
    Thanks,
    Sree.

    data: lv_value type < type of REPORTS attribute>.
    wd_context->get_attribuet( name = 'REPORTS' value = lv_value ).
    Abhi

  • SAP Inbound error

    Hi,
      I am doing file to IDOC. The message is showing Successful but it is was going to R/3. I am giving there that xml message which generated in SXMB_MONI.
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Response
      -->
    - <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
    - <SOAP:Header>
    - <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
      <SAP:MessageClass>ApplicationMessage</SAP:MessageClass>
      <SAP:ProcessingMode>asynchronous</SAP:ProcessingMode>
      <SAP:MessageId>70C7D170-4D1F-11DB-C92E-000D60E1FBDF</SAP:MessageId>
      <SAP:TimeSent>2006-09-26T05:25:36Z</SAP:TimeSent>
    - <SAP:Sender>
      <SAP:Service>BS_KAREEM_3RDPARTY</SAP:Service>
      <SAP:Interface namespace="http://file2ZIDOC_Kareem">MI_FILE2IDOC_KAREEM</SAP:Interface>
      </SAP:Sender>
    - <SAP:Receiver>
      <SAP:Party agency="" scheme="" />
      <SAP:Service>BS_R3_SYSTEM</SAP:Service>
      <SAP:Interface namespace="urn:sap-com:document:sap:idoc:messages">ZMTIDOCIN.ZIDOCIN</SAP:Interface>
    - <SAP:Mapping notRequired="M">
      <SAP:ObjectId>Mrkk5K/IO/2cNNOwFbUlQg==</SAP:ObjectId>
      <SAP:SWCV>/fKMsErhEduTP/v6CjIBJA==</SAP:SWCV>
      <SAP:SP>-1</SAP:SP>
      </SAP:Mapping>
      </SAP:Receiver>
      <SAP:Interface namespace="urn:sap-com:document:sap:idoc:messages">ZMTIDOCIN.ZIDOCIN</SAP:Interface>
      </SAP:Main>
    - <SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:QualityOfService>ExactlyOnce</SAP:QualityOfService>
      </SAP:ReliableMessaging>
    - <SAP:HopList xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
    - <SAP:Hop timeStamp="2006-09-26T05:25:36Z" wasRead="false">
      <SAP:Engine type="AE">af.x11.apollo</SAP:Engine>
      <SAP:Adapter namespace="http://sap.com/xi/XI/System">XIRA</SAP:Adapter>
      <SAP:MessageId>70C7D170-4D1F-11DB-C92E-000D60E1FBDF</SAP:MessageId>
      <SAP:Info />
      </SAP:Hop>
    - <SAP:Hop timeStamp="2006-09-26T05:25:37Z" wasRead="false">
      <SAP:Engine type="IS">is.01.apollo</SAP:Engine>
      <SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
      <SAP:MessageId>70C7D170-4D1F-11DB-C92E-000D60E1FBDF</SAP:MessageId>
      <SAP:Info>3.0</SAP:Info>
      </SAP:Hop>
    - <SAP:Hop timeStamp="2006-09-26T05:25:37Z" wasRead="false">
      <SAP:Engine type="IS" />
      <SAP:Adapter namespace="http://sap.com/xi/XI/System">IDoc</SAP:Adapter>
      <SAP:MessageId>70C7D170-4D1F-11DB-C92E-000D60E1FBDF</SAP:MessageId>
      <SAP:Info>0000000000004003;</SAP:Info>
      </SAP:Hop>
      </SAP:HopList>
    - <SAP:IDocOutbound xmlns:SAP="http://sap.com/xi/XI/Message/30">
      <SAP:TABNAM>EDI_DC40</SAP:TABNAM>
      <SAP:MANDT>001</SAP:MANDT>
      <SAP:DOCREL>700</SAP:DOCREL>
      <SAP:DOCNUM>0000000000004003</SAP:DOCNUM>
      <SAP:DIRECT>2</SAP:DIRECT>
      <SAP:IDOCTYP>ZIDOCIN</SAP:IDOCTYP>
      <SAP:CIMTYP />
      <SAP:MESTYP>ZMTIDOCIN</SAP:MESTYP>
      <SAP:MESCOD />
      <SAP:MESFCT />
      <SAP:SNDPOR>SAPX11</SAP:SNDPOR>
      <SAP:SNDPRN>C11CLNT001</SAP:SNDPRN>
      <SAP:SNDPRT>LS</SAP:SNDPRT>
      <SAP:SNDPFC />
      <SAP:RCVPOR>SAPA11</SAP:RCVPOR>
      <SAP:RCVPRN>A11CLNT200</SAP:RCVPRN>
      <SAP:RCVPRT>LS</SAP:RCVPRT>
      <SAP:RCVPFC />
      <SAP:TEST />
      <SAP:SERIAL />
      <SAP:EXPRSS />
      <SAP:STD />
      <SAP:STDVRS />
      <SAP:STATUS />
      <SAP:OUTMOD />
      <SAP:SNDSAD />
      <SAP:SNDLAD />
      <SAP:RCVSAD />
      <SAP:RCVLAD />
      <SAP:STDMES />
      <SAP:REFINT />
      <SAP:REFGRP />
      <SAP:REFMES />
      <SAP:CREDAT>0000-00-00</SAP:CREDAT>
      <SAP:CRETIM>00:00:00</SAP:CRETIM>
      <SAP:ARCKEY>70C7D1704D1F11DBC92E000D60E1FBDF</SAP:ARCKEY>
      </SAP:IDocOutbound>
    - <SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
      <SAP:Date>20060926</SAP:Date>
      <SAP:Time>105537</SAP:Time>
      <SAP:Host>apollo</SAP:Host>
      <SAP:SystemId>X11</SAP:SystemId>
      <SAP:SystemNr>01</SAP:SystemNr>
      <SAP:OS>Windows NT</SAP:OS>
      <SAP:DB>ORACLE</SAP:DB>
      <SAP:Language />
      <SAP:ProcStatus>003</SAP:ProcStatus>
      <SAP:AdapterStatus>007</SAP:AdapterStatus>
      <SAP:User>PIAFUSER</SAP:User>
      <SAP:TraceLevel>1</SAP:TraceLevel>
      <SAP:LogSeqNbr>002</SAP:LogSeqNbr>
      <SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr>
      <SAP:PipelineIdInternal>SAP_CENTRAL</SAP:PipelineIdInternal>
      <SAP:PipelineIdExternal>CENTRAL</SAP:PipelineIdExternal>
      <SAP:PipelineElementId />
      <SAP:PipelineStartElementId>5EC3C53B4BB7B62DE10000000A1148F5</SAP:PipelineStartElementId>
      <SAP:PipelineService />
      <SAP:QIdInternal>XBTO2___0002</SAP:QIdInternal>
      <SAP:CommitActor>X</SAP:CommitActor>
      <SAP:SplitNumber>0</SAP:SplitNumber>
      <SAP:NumberOfRetries>0</SAP:NumberOfRetries>
      <SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries>
      <SAP:TypeOfEngine client="001">CENTRAL</SAP:TypeOfEngine>
      <SAP:PlsrvExceptionCode />
      <SAP:EOReferenceRuntime type="TID">0A32012412084518B9D10012</SAP:EOReferenceRuntime>
      <SAP:EOReferenceInbound type="TID" />
      <SAP:EOReferenceOutbound type="TID">0A32012412084518B9D10013</SAP:EOReferenceOutbound>
      <SAP:MessageSizePayload>1004</SAP:MessageSizePayload>
      <SAP:MessageSizeTotal>3457</SAP:MessageSizeTotal>
      <SAP:PayloadSizeRequest>1004</SAP:PayloadSizeRequest>
      <SAP:PayloadSizeRequestMap>650</SAP:PayloadSizeRequestMap>
      <SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse>
      <SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap>
      <SAP:Reorganization>INI</SAP:Reorganization>
      <SAP:AdapterInbound>AENGINE</SAP:AdapterInbound>
      <SAP:AdapterOutbound>IDOC</SAP:AdapterOutbound>
      <SAP:InterfaceAction>DEL</SAP:InterfaceAction>
      <SAP:RandomNumber>13</SAP:RandomNumber>
      <SAP:AckStatus>000</SAP:AckStatus>
      <SAP:SkipReceiverDetermination />
      <SAP:Receiver_Agreement_GUID>773C6AD79B4C3C31ACD5CE98876A9904</SAP:Receiver_Agreement_GUID>
      <SAP:Serialize_Children>X</SAP:Serialize_Children>
      </SAP:RunTime>
    - <SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30">
    - <SAP:RunTimeItem>
      <SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
      <SAP:Timestamp type="begin" host="apollo">20060926052536.997</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
      <SAP:Timestamp type="end" host="apollo">20060926052537.013</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
      <SAP:Timestamp type="begin" host="apollo">20060926052537.013</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
      <SAP:Timestamp type="end" host="apollo">20060926052537.028</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
      <SAP:Timestamp type="begin" host="apollo">20060926052537.028</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
      <SAP:Timestamp type="end" host="apollo">20060926052537.216</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="begin" host="apollo">20060926052537.216</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="end" host="apollo">20060926052537.216</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="begin" host="apollo">20060926052537.216</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="end" host="apollo">20060926052537.232</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
      <SAP:Timestamp type="begin" host="apollo">20060926052537.232</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
      <SAP:Timestamp type="end" host="apollo">20060926052537.232</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name>
      <SAP:Timestamp type="begin" host="apollo">20060926052537.232</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name>
      <SAP:Timestamp type="end" host="apollo">20060926052537.325</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
      <SAP:Timestamp type="begin" host="apollo">20060926052537.325</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
      <SAP:Timestamp type="end" host="apollo">20060926052537.419</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>
      <SAP:Timestamp type="begin" host="apollo">20060926052537.419</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>
      <SAP:Timestamp type="end" host="apollo">20060926052537.45</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_CALL_ADAPTER</SAP:Name>
      <SAP:Timestamp type="begin" host="apollo">20060926052537.45</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_CALL_ADAPTER</SAP:Name>
      <SAP:Timestamp type="end" host="apollo">20060926052537.466</SAP:Timestamp>
      </SAP:RunTimeItem>
      </SAP:PerformanceHeader>
    - <SAP:Diagnostic xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:TraceLevel>Information</SAP:TraceLevel>
      <SAP:Logging>Off</SAP:Logging>
      </SAP:Diagnostic>
    - <SAP:OutboundBinding xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
    - <SAP:OutboundBindingEntry version="30">
      <SAP:OutboundBindingObjectId>773C6AD79B4C3C31ACD5CE98876A9904</SAP:OutboundBindingObjectId>
      <SAP:FromPartyName />
      <SAP:FromServiceName>BS_KAREEM_3RDPARTY</SAP:FromServiceName>
      <SAP:ToPartyName />
      <SAP:ToServiceName>BS_R3_SYSTEM</SAP:ToServiceName>
      <SAP:ToInterfaceName>ZMTIDOCIN.ZIDOCIN</SAP:ToInterfaceName>
      <SAP:ToInterfaceNamespace>urn:sap-com:document:sap:idoc:messages</SAP:ToInterfaceNamespace>
    - <SAP:OutboundBindingAttributes>
      <SAP:AdapterTypeData xmlns:SAP="http://sap.com/xi/XI/Message/30" />
      </SAP:OutboundBindingAttributes>
    - <SAP:HeaderMapping>
    - <SAP:FieldMapping xmlns:SAP="http://sap.com/xi/XI/Message/30">
    - <SAP:Field>
      <SAP:Name>ReceiverService</SAP:Name>
      <SAP:ExtractorId>604DD4C04D1F11DB98B1000E7FF4C3A7</SAP:ExtractorId>
      </SAP:Field>
    - <SAP:Field>
      <SAP:Name>SenderService</SAP:Name>
      <SAP:ExtractorId>5D504C304D1F11DBB7BD000E7FF4C3A7</SAP:ExtractorId>
      </SAP:Field>
      </SAP:FieldMapping>
      </SAP:HeaderMapping>
    - <SAP:ChannelEntry version="30">
      <SAP:PartyName xmlns:SAP="http://sap.com/xi/XI/Message/30" />
      <SAP:ServiceName xmlns:SAP="http://sap.com/xi/XI/Message/30">BS_R3_SYSTEM</SAP:ServiceName>
      <SAP:ChannelName xmlns:SAP="http://sap.com/xi/XI/Message/30">CC_File2ZIdoc_Receiver_kareem</SAP:ChannelName>
      <SAP:AdapterName xmlns:SAP="http://sap.com/xi/XI/Message/30">IDoc</SAP:AdapterName>
      <SAP:AdapterNamespace xmlns:SAP="http://sap.com/xi/XI/Message/30">http://sap.com/xi/XI/System</SAP:AdapterNamespace>
      <SAP:AdapterSWCV xmlns:SAP="http://sap.com/xi/XI/Message/30">B38BCD00E47111D7AFACDE420A1145A5</SAP:AdapterSWCV>
      <SAP:AdapterEngineType xmlns:SAP="http://sap.com/xi/XI/Message/30">IS</SAP:AdapterEngineType>
      <SAP:AdapterEngineName xmlns:SAP="http://sap.com/xi/XI/Message/30" />
      <SAP:MessageProtocol xmlns:SAP="http://sap.com/xi/XI/Message/30">IDoc</SAP:MessageProtocol>
      <SAP:MessageProtocolVersion xmlns:SAP="http://sap.com/xi/XI/Message/30" />
      <SAP:TransportProtocol xmlns:SAP="http://sap.com/xi/XI/Message/30">IDoc</SAP:TransportProtocol>
      <SAP:TransportProtocolVersion xmlns:SAP="http://sap.com/xi/XI/Message/30" />
      <SAP:ChannelDirection xmlns:SAP="http://sap.com/xi/XI/Message/30">O</SAP:ChannelDirection>
      <SAP:FromPartyAgency xmlns:SAP="http://sap.com/xi/XI/Message/30" />
      <SAP:FromPartySchema xmlns:SAP="http://sap.com/xi/XI/Message/30" />
      <SAP:ToPartySchema xmlns:SAP="http://sap.com/xi/XI/Message/30" />
      <SAP:ToPartyAgency xmlns:SAP="http://sap.com/xi/XI/Message/30" />
    - <SAP:ChannelAttributes xmlns:SAP="http://sap.com/xi/XI/Message/30">
    - <SAP:AdapterTypeData xmlns:SAP="http://sap.com/xi/XI/Message/30">
    - <SAP:Attribute>
      <SAP:Name>interfaceVersion</SAP:Name>
      <SAP:Value>3</SAP:Value>
      </SAP:Attribute>
    - <SAP:Attribute>
      <SAP:Name>passControlSetValues</SAP:Name>
      <SAP:Value>1</SAP:Value>
      </SAP:Attribute>
    - <SAP:Attribute>
      <SAP:Name>passReceiverValue</SAP:Name>
      <SAP:Value>0</SAP:Value>
      </SAP:Attribute>
    - <SAP:Attribute>
      <SAP:Name>passSenderValue</SAP:Name>
      <SAP:Value>0</SAP:Value>
      </SAP:Attribute>
    - <SAP:Attribute>
      <SAP:Name>port</SAP:Name>
      <SAP:Value>SAPA11</SAP:Value>
      </SAP:Attribute>
    - <SAP:Attribute>
      <SAP:Name>queueing</SAP:Name>
      <SAP:Value>0</SAP:Value>
      </SAP:Attribute>
    - <SAP:Attribute>
      <SAP:Name>restoreOriginalParty</SAP:Name>
      <SAP:Value>0</SAP:Value>
      </SAP:Attribute>
    - <SAP:Attribute>
      <SAP:Name>rfcDestination</SAP:Name>
      <SAP:Value>RFC_ZEUS_ABAP</SAP:Value>
      </SAP:Attribute>
    - <SAP:Attribute>
      <SAP:Name>sapRelease</SAP:Name>
      <SAP:Value>700</SAP:Value>
      </SAP:Attribute>
    - <SAP:Attribute>
      <SAP:Name>segmentVersion</SAP:Name>
      <SAP:Value />
      </SAP:Attribute>
      </SAP:AdapterTypeData>
      </SAP:ChannelAttributes>
      </SAP:ChannelEntry>
      </SAP:OutboundBindingEntry>
      </SAP:OutboundBinding>
    - <SAP:System xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Record namespace="http://sap.com/xi/XI/Message/30/general" name="senderAgreementGUID">def5775cf87c3aee8e94b2e814a8791b</SAP:Record>
      </SAP:System>
    - <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
      <Trace level="1" type="T">Party normalization: sender</Trace>
      <Trace level="1" type="T">Sender scheme external = XIParty</Trace>
      <Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>
      <Trace level="1" type="T">Sender party external =</Trace>
      <Trace level="1" type="T">Sender party normalized =</Trace>
      <Trace level="1" type="T">Party normalization: receiver</Trace>
      <Trace level="1" type="T">Receiver scheme external =</Trace>
      <Trace level="1" type="T">Receiver agency external =</Trace>
      <Trace level="1" type="T">Receiver party external =</Trace>
      <Trace level="1" type="T">Receiver party normalized =</Trace>
      <Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>
      <Trace level="1" type="T">COMMIT is done by XMB !</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
      <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
      <Trace level="1" type="T">****************************************************</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">XMB entry processing</Trace>
      <Trace level="1" type="T">system-ID = X11</Trace>
      <Trace level="1" type="T">client = 001</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = PIAFUSER</Trace>
      <Trace level="1" type="Timestamp">2006-09-26T05:25:37Z CET</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">****************************************************</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Message-GUID = 70C7D1704D1F11DBC92E000D60E1FBDF</Trace>
      <Trace level="1" type="T">PLNAME = CENTRAL</Trace>
      <Trace level="1" type="T">QOS = EO</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
      <Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
      <Trace level="1" type="T">Queue name : XBTI0006</Trace>
      <Trace level="1" type="T">Generated prefixed queue name = XBTI0006</Trace>
      <Trace level="1" type="T">Schedule message in qRFC environment</Trace>
      <Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Going to persist message</Trace>
      <Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
      <Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
      <Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
      <Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
      <Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
      <Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
      <Trace level="1" type="T">system-ID = X11</Trace>
      <Trace level="1" type="T">client = 001</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = PIAFUSER</Trace>
      <Trace level="1" type="Timestamp">2006-09-26T05:25:37Z CET</Trace>
      <Trace level="1" type="T">----
    </Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC">
      <Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
      <Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
    - <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
      <Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
      <Trace level="1" type="T">Cache Content is up to date</Trace>
      </Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
    - <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
      <Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
      <Trace level="1" type="T">Cache Content is up to date</Trace>
      </Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
      <Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" />
    - <!--  ************************************
      -->
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
      <Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">number of receivers: 1</Trace>
      <Trace level="1" type="T">Single-receiver split case</Trace>
      <Trace level="1" type="T">Post-split internal queue name = XBTO2___0002</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Persisting single message for post-split handling</Trace>
      <Trace level="1" type="T" />
      <Trace level="1" type="T">Going to persist message + call qRFC now...</Trace>
      <Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
      <Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
      <Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
      <Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
      <Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
      <Trace level="1" type="T">system-ID = X11</Trace>
      <Trace level="1" type="T">client = 001</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = PIAFUSER</Trace>
      <Trace level="1" type="Timestamp">2006-09-26T05:25:37Z CET</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
      <Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
      <Trace level="1" type="T">Start with pipeline element PLEL= 5EC3C53B4BB7B62DE10000000A1148F5</Trace>
    - <Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV">
      <Trace level="1" type="T">Interface Mapping http://file2ZIDOC_Kareem MI_FILE2IDOC_KAREEM</Trace>
      </Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
    - <Trace level="1" type="B" name="PLSRV_OUTBOUND_BINDING">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
      <Trace level="1" type="B" name="CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV" />
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
    - <Trace level="1" type="B" name="PLSRV_CALL_ADAPTER">
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">---- Outbound IDoc-Adapter -
    </Trace>
      <Trace level="1" type="T">----
    </Trace>
    - <Trace level="1" type="B" name="CL_IDX_IDOC_SERVICE-ENTER_PLSRV">
      <Trace level="1" type="T">Pipeline Service ID: PLSRV_CALL_ADAPTER</Trace>
      <Trace level="1" type="T">Get Information from IS-Header Objekt</Trace>
      <Trace level="1" type="T">Get Information from SD-IDoc-Endpoint</Trace>
      <Trace level="1" type="T">Sender and Receiver after Header-Mapping</Trace>
      <Trace level="1" type="T">Sender service BS_KAREEM_3RDPARTY</Trace>
      <Trace level="1" type="T">Receiver service BS_R3_SYSTEM</Trace>
      <Trace level="1" type="T">Get IDoc-XML from the Resource Objekt</Trace>
    - <Trace level="1" type="B" name="IDX_XML_TO_IDOC">
      <Trace level="1" type="T">Parse XML-BODY</Trace>
      <Trace level="1" type="T">Get the Metadata for port SAPA11</Trace>
      <Trace level="1" type="T">Convert one IDoc</Trace>
      <Trace level="1" type="T">Warning: IDoc does not contain control-record</Trace>
      <Trace level="1" type="T">Make Syntax check of actual Idoc</Trace>
      <Trace level="1" type="T">Convert Segment-Types to Segment-Definitions</Trace>
      </Trace>
      <Trace level="1" type="T">Call Outbound IDoc-Adapter</Trace>
      <Trace level="1" type="T">Call Outbound IDoc-Adapter</Trace>
    - <Trace level="1" type="B" name="IDX_OUTBOUND_XMB">
      <Trace level="1" type="T">FM IDOC_INBOUND_ASYNCHRONOUS with RFCDEST= RFC_ZEUS_ABAP</Trace>
      </Trace>
      </Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
      </Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Async processing completed OK.</Trace>
      <Trace level="1" type="T">system-ID = X11</Trace>
      <Trace level="1" type="T">client = 001</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = PIAFUSER</Trace>
      <Trace level="1" type="Timestamp">2006-09-26T05:25:37Z CET</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      </SAP:Trace>
      </SOAP:Header>
    - <SOAP:Body>
    - <SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7">
    - <SAP:Payload xlink:href="cid:[email protected]">
      <SAP:Name>MainDocument</SAP:Name>
      <SAP:Description />
      <SAP:Type>Application</SAP:Type>
      </SAP:Payload>
      </SAP:Manifest>
      </SOAP:Body>
      </SOAP:Envelope>
    THX.

    Ansar,
    The note : 837595 would give the list of authorizations.
    <i>************************************************************************************************************
    Summary
    Symptom
    Loading the IDoc metadata from the reference system terminates with the following error message:
    "Metadata EDISDEF for port, IDoc type and CIM type not maintained".
    Other terms
    IDoc adapter, metadata, EDISDEF, IDX2, authorization, Release 4.6C
    Reason and Prerequisites
    You use the IDoc Adapter in the Exchange Infrastructure and you try to use the IDocs to receive or send data. For these IDocs, an attempt is made to load the IDoc metadata from an R/3 reference system with an SAP NetWeaver Release lower than 6.20.
    This occurs either at runtime, whereby the relevant messages run into 'System error' status, or when you use transaction IDX2 during manual loading of the metadata. In this case, the reference ystem is called by RFC and the logon user of the RFC destination does not have the necessary authorizations for determining the metadata.
    Solution
    In transaction PFCG, extend the role of the logon user by adding the following authorizations:
    Authorization object S_RFC
    Field name RFC_TYPE value FUGR
    Field name RFC_NAME value EDIMEXT, SDTX
    Field name ACTVT    value 16
    Authorization object S_IDOCDEFT
    Field name ACTVT   value 03
    Field name EDI_CIM value ' '
    Field name EDI_DOC value TXTRAW01
    Field name EDI_TCD value WE30
    Authorization object S_CTS_ADMI
    Field name CTS_ADMFCT  value TABL
    Authorization object S_TABU_DIS
    Field name ACTVT      value 03
    Field name DICBERCLS  value
    Note: You can activate the display of the technical names of objects and fields in authorizations maintenance by choosing the 'Technical Names' function from the 'Utilities' menu.
    Then save and execute the 'Generate' function. Then choose 'Back' to return to role maintenance and switch to the 'Users' tab. Press the 'User comparison' button to execute this function.
    ************************************************************************************************************</i>
    Regards,
    Bhavesh

  • Saving default values for checkboxes

    Hi all,
    one of our customers has recently upgraded ´their NW7.00 (SAP ECC 6.0) system to basis SP18. As a result of this, it is no longer possible for users to save default values, in Web Dynpro ABAP applications, neither for checkboxes nor for radiobuttons.
    This worked fine before the application of the support package. The user could simply right click the UI element and select "Use current value sas default" from the context menu, as is still the case for all other input-enabled UI elements.
    This option is simply no longer available in the context menu for checkboxes & radiobuttons.
    I have had a look through the OSS notes in the SP and also the "Side-Effects" report, but can't find anything to indicate that this has been done deliberately by SAP.
    Before I raise this as a question to SAP, does anbody out there have any more information on this issue. Is it a bug or a feature?
    Thanks,
    Mike Speight

    Hi Mike Speightl,
    You can save the default values in the Webdynpro by using the Method (WD_DO_INT).
    For exp :
    If Emp is your Node name.
    ID and Name are your attributes in which you wish to put default values after execution:
    lo_el_emp->set_attribute( exporting name = 'ID' value = '1001' ).
    lo_el_emp->set_attribute( exporting name = 'NAME' value = 'SAP' ).
    When you execute your application, it will display default values in ID : 1001
                                                                                    Name : SAP
    Just before loading any view, this method will be executed :  WD_DO_INT
    If you are referring to default chkbox selected after executing then refer to the concept   Initialize lead selection
    If this is not the issue then please let me know.
    Regards,
    Kittu
    Edited by: Kittu on Nov 16, 2009 4:05 AM

Maybe you are looking for

  • ITunes match completed on computer but wont work on iPhone...Please help!

    I have an interesting situation. I have a developers license (if only to get iOS for my iPhone before anyone else does.... lol). Before the public launch of the iOS 5 and iTunes Match and iCloud, I set up a "Developer ID". Match worked beautifuly for

  • Installing oracle db in linux, how to know if it's running?

    Hi all, I have installed oracle 9i in my red hat linux box, but I'm getting few problems (Logging as root): 1) if I type lsnrctl status i get: Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC)) STATUS of the LISTENER Alias LISTENER Vers

  • Release 1.5, 'enum' is a keyword, and may not be used as an identifier.help

    hello i am working for a MNC and i am trying to build my prduct in JDK1.5 and i am getting this error... ...release 1.5, 'enum' is a keyword, and may not be used as an identifier... the probelm is that i cant go to 1.4 as my product suports only 1.5

  • Continue the package execution even if task fails

    I have a send mail task in my package which sends start and end mails of the package. If the SMPT server is down and not working entire process stops as send mail task fails. Is there a way that if the SMPT server is down and also if the send mail ta

  • Hiding Infotype Start Date in the header

    Hi I need to hide the infotype start date begda for a particular infotype 8. I tried all these tables but could not find an option to hide bedga T588m V_582A_B V_T588I T588J Looking forward for some inputs Thanks