Release Transfer - S/W Component Version - Conflict

Hello Alll,
I did a release transfer of a particular Namespace from S/W Component Version u2013 1.0 to 2.0. By transfer I didnu2019t get any error message, but after the transfer, I found some of the message types still shows the older S/W component version i.e. 1.0.
This happens only in u201CProcess Integration Scenariou201D that too partly.  Other components of the name space displays right version i.e. 2.0. If anyone overcame such a situation, please let me know the procedure to avoid such a conflict.
Best Regards,
Satishkumar, Dhamodharam.

Satish,
Either you or someone else might have changed the process integration  scenario manually in 2.0 version that is causing conflict.
You can check the history and object versions to make sure who did it and what has been done during this manual change.
If the manual change done is not necessary then go to conflict tab, click on the object and select the latest 2.0 version object (displayed object button) and save it
To avoid this happening from next time, do not make changes to 2.0.... watever changes are required, do it in 1.0 and do a release transfer
Venkat.

Similar Messages

  • PI 7.0 - Design - Release Transfer Question

    Hi,
    i created a new SWCV to extend a consisting integration scenario design. I'd like to copy the existing objects from the "old" SWCV 2.00 into the "new" SWCV 2.01. I'd like to use the function "Release Transfer", so that i have to change the consisting objects only in one place. I also want avoid to copy-paste all objects and namespaces.
    Is this possible? If yes, how can i do this? Are there any howTo's or blogs.
    If i just use the wizard, in the end i got always the same error:
    Object Interface Mapping IM_History_ALG2IF | http://mynamespace/mapping cannot be imported into software component version SC_JDA , 2.01 of jda.com because it's namespace is not permitted there Define the relevant namespaces in the target version before executing the release transfer
    Thanks in advance
    Michael

    Hi
    By using release transfer function, you can transfer design objects within an Integration Repository to other software component versions as follows:
    1) From a current software component version to the subsequent version, once development in the current version is finished
    2) From a software component version to an older version of the same software component, for example to make a correction available in an older version.
    3) From a software component version to a version of another software component. For example, this may be necessary because you may want to stop objects of software components that are based on each other from being available in the sub-software component, and only make them available in the superior software component.
    Pls check the following links for details
    http://help.sap.com/saphelp_nw04/helpdata/en/e8/e8573ba5f13048be50532fc3fcea9c/content.htm
    Regards
    Abhijit

  • Problem with release-transfer

    Hi,
    I have created a new softwarecomponent version and I've tried I release-transfer.
    It worked fine but in the old softwarecomponent version there where "imported objects" (IDocs) and these IDocs are not in the new softwarecomponent version.
    Does anybody know how to get these Idocs into new softwarecomponent version?
    Thanks.
    Regards
    Stefan

    Hi.
    In your new softwarecomponent, you need to click the tap:
    Import of RFC and IDoc Interfaces from SAP system permitted.
    Its located under the software component itself!
    You need to fill out System, Client, Message Server and Group.
    Regards Peter

  • Release transfer

    Hi guys,
    I understand that release transfer is used to move objects from one SWC version to another .
    I am having a new SWCV SRM server 7.0 ( PI content )  and a older swcv POscenarios ( having custom mappings using objects in SRM server 3.0 )
    In my case i am using release transfer  to copy object from a new  software component version to an older version of the same software component, for example to make a correction available in an older version.
    However I am concerned about the custom mappings in the SWCV POscenarios because if the structure of message type changes the mapping will go away.
    Is there any way to do this such that the mapping does not get affected.

    What Michal said is the easiest way, but if you Basis team wants more details then just do this....
    To find out exactly with Role you're missing just use transaction su53. It will display User Authorization info. You'll see where it says "You are not authorized to...." Someone from you Basis team should be able to find out which Role has the missing object. Then they would just add you to the Role. This is assuming you have access to su53.
            - Emmett

  • Error in release transfer

    Hi,
    When i do a release transfer i get a Error message "Object Message Mapping MM_aa | http://bb cannot be imported into software component version TARGET, 1.0 of target because it's namespace is not permitted there Define the relevant namespaces in the target version before executing the release transfer"
    I tried having the same Namespaces in both the SWCVs but dint work (It threw a warning ofcurse that the namespace is same)...
    Any clues??

    hey pavan bhai
    release transfer should work by steps what have you followed only requirement is to have create the similar namespace in the target software component first and then do the release transfer.
    one thing jsut try unchecking the target SWCV (original objects option at down it should work then)
    how is life there?
    reards
    Nisar

  • Can we change the Software Component Version's Name?

    Hi everyone,
    Can we change the Software Component Version's Name in the Integration Repository? If we can, how can we change it?
    Regards,
    Nick

    hi Nick,
    Procedure:
    1. create a new software component in SLD
    2. create a new version of this software component in SLD
    3. import in into the repository
    4. try using release transfer to transfer objects
    from old on to the new one
    http://help.sap.com/saphelp_nw04/helpdata/en/e8/e8573ba5f13048be50532fc3fcea9c/content.htm
    5.delete the old software component
    /people/siva.maranani/blog/2005/05/22/how-to-delete-software-component-from-integration-builder
    BTW
    <b>do not chage it in the database!</b>
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

  • Possible version conflict, sending purchase order to SUS in MM-SUS scenario

    We are currently trying to get the MM-SUS scenario working. In this
    scenario, we create a purchase order in the ERP/MM system. The
    purchase order is then transferred into SUS via XI/PI.
    After creating a purchase order in the MM system, the purchase order
    reaches the SUS system, but then errors-out in the SUS system upon
    posting. The specific error is paraphrased as follows:
    No interface action for sender or receiver found (from Trace)
    PARSE_APPLICATION_DATA
    CX_ST_MATCH_ELEMENT
    System expected the element http://sap.com/xi/SAPGlobal20/Global;
    PurchaseOrderRequest
    We suspect a version conflict. The SUS version is 7.01. The XI/PI
    system is version 7.11.
    Can you confirm or rule-out a version conflict?
    The Integration Builder scenario we are using is Plan
    Driven Procurement with Supplier Enablement.
    We have tryed many variations in Integration Builder, but all
    produce errors in SUS.  The test tool in Integration Builder also shows errors
    for certain message types.  The message type ORDERS.ORDERS02
    needed to be added manually, and did not come along with the scenario.
    Edited by: Bill Guderian on Mar 19, 2010 4:53 PM

    Any clue from here.
    Note 936003 - ERS Invoice causes conversion error within SRM
    When the SRM system attempts to process an ERS Invoice sent from the MM backend, a PARSE_APPLICATION_DATA CX_ST_DESERIALIZATION_ERROR fault is thrown.
    Other terms
    CX_ST_DESERIALIZATION_ERROR PARSE_APPLICATION_DATA SUS SRM EBP ERS Invoice XI Exchange Infrastructure Mapping
    Reason and Prerequisites
    This error will occur when the IDOC does not have a VPREI value; it is the result of an error within the divide logic of the XI mapping operation.  This operation is performed within the XI system.  A calculation of NETWR/MENGE is performed; however, the result is not properly formatted.  As such, 72.30/10 produces a result of 7.2300002. This value is too long for the inbound SRM proxy and hence the error is thrown.
    Solution
    The solution to this problem is to add a FORMATNUM function within the XI mapping operation.  This restricts the result to 2 decimal places, which adheres to the definition of the inbound proxy.
    Step by step directions on how one implements the FORMATNUM function are as follows:
    1. Log into the XI system with SAPGUI
    2. Start the Integration Builder:Design tool (for steps on how to do this, review the steps below):
        a. Run transaction sxmb_ifr
        b. This will cause a browser to come up.  Select the Integration Repository link
    3. In the left pane, select the Objects tab
    4. Navigate to the SAP SRM SERVER ' SAP SRM SERVER 5.0 ' http://sap.com/xi/SRM/SupplierEnablement/Global --> Mapping Objects --> Message Mappings folder
    5. Double-click on MM2SUSInvoice
    6. The right pane will display the mapping object
    7. Select Edit mode
    8. In the box that contains the output (Message Type: InvoiceRequest), navigate to InvoiceRequest ' Invoice ' Item ' Price ' NetUnitPrice
    9. Double-click on the Amount element and you should see the mapping, represented graphically in the bottom pane
    10. In the status line of the graphical editor, select Arithmetic from the list box:
    11. To the right of the listbox, scroll until you see the FormatNum function
    12. Click on FormatNum, which will cause the function to be added to the graphical editor.  You may drag the box as desired
    13. Select the connection that binds the if/then/else to the Amount box by grabbing the arrow within the input of the Amount
    14. Release the drag of the connection while over the input to the FormatNum box.  This will reassign the output of the if/then/else to the input of FormatNum
    15. Create a connection between the output of the FormatNum box and the input of the Amount box.  You accomplish this by clicking within the output and releasing within the input (respectively).
    16. Save the modified mapping object
    17. Activate the changes
        a. In the left pane, select the Change Lists tab
        b. Navigate to the Standard Change List entry
        c. Right-click the Standard Change List entry and select Activate
        d. Select only MM2SUSInvoice if more than one item is available, and press the Activate button
    18. This will complete the required modification.

  • Unable to import software component version in IR

    Why i can't import software component version in IR by Tools->Transfer from SLD->import software component version?
    error message is "Unable to determine dependencies of software component version"
    i just create it in SLD before, anything else need to do?
    please give me some information, Thanks!

    Hi Robert,
    Please cross check with this blog on how to create a SWCV and import in IR.
    /people/srinivas.vanamala2/blog/2007/02/05/step-by-step-guide-xml-file-2-xml-file-scenario-part-i
    Regards,
    Sachin

  • How to update objects of sub software component version?

    I have two SWCV, say SWCV_BASE and SWCV_DERIVE, SWCV_DERIVE is based on SWCV_BASE. So the objects which belong to SWCV_BASE are also availabe in the BASIC OBJECTS directory under SWCV_DERIVE.
    My question is:
    When I make some change in SWCV_BASE, how to reflect this modification to the SWCV_DERIVE? Currently whatever I do to SWCV_BASE, the change can't be transferd to BASIC OBJECTS in SWCV_DERIVE. Does anyone know how to syncronize the objects in SWCV_DERIVE to get the newest ojbects in SWCV_BASE.
    MUST REWARD FOR GOOD ANSWERS.
    Regards,
    Hui

    Hi, Michal
    I forget to activate it. Yes, it's really...  Forgive me:)
    I have another question which has confused me for long time. It would be apprecaited if you could give me some light. According to sap documentation, through sub software component version we can reuse or do some customer modification to some SAP XI OBJECTS. But when I import some SAP software component version like SAP BASIS 6.20, I find nothing inside it. So when, how and where can we use SAP XI OBJECTS?
    See the scenaio below:
    An R/3 system is going to transfer data with a database.
    R/3 (IDoc) <-> Database (JDBC)
    IDocs can be devided into two types:
    1. idocs shipped by SAP.
    2. customized idocs.
    In my understanding, when I import some sap software component version like SAB BASIS 6.20. I should be able to find the SAP shipped idocs. But nothing is there.
    So Should I import the SAP shipped idocs into the SAP software component version? Then create a customized software component version based on SAP component version, where I import the customiyed idocs.
    Could you give me some advice?
    Thanks in advance.
    Regards,
    Hui Wang

  • Version conflict between XE's ODP and VS2005/ODT's ODP

    Suppose you've just built an application with VS2005, .NET Framework 2.0, and Oracle Developer Tools for Visual Studio .NET with Oracle10g Release 2 ODAC 10.2.0.2.20 which uses Oracle.DataAccess.dll version 2.102.2.20. You want to be able to run the application on a client machine that has an Oracle XE database installed locally. Perhaps you even require that the client machine runs the Oracle XE Client. Unfortunately, even with both there seems to be a version conflict regarding Oracle.DataAccess.dll. Can anyone say what are the best practices for such a situation?

    Situation:
    1) Oracle XE (database with/without client) installs with the following two files in the <ORACLEXE_SERVER_HOME>/BIN directory:
    Oracle.DataAccess.dll v10.2.0.100 (for .NET Framework 1.0)
    OraOps10.dll v10.2.0.100 (for .NET Framework 1.0)
    2) Applications built with VS2005, .NET Framework 2.0, and Oracle Developer Tools for Visual Studio .NET with Oracle10g Release 2 ODAC 10.2.0.2.20 use Oracle.DataAccess.dll v2.102.2.20 (for .NET Framework 2.0).
    3) The client machine will be missing the following two files vital to the application: Oracle.DataAccess.dll v2.102.2.20 (for .NET Framework 2.0), OraOps10w.dll v2.102.2.20 (for .NET Framework 2.0). These two files can be found on the development machine in the <ORACLE_ODAC HOME>/odp.net/bin/2.x  and <ORACLEODAC _HOME>/bin directories, respectively.
    Action:
    When installing the application on the client's machine, place copies of the two missing files into the client's <ORACLEXE_SERVER_HOME>/BIN directory, overwriting the existing Oracle.DataAccess.dll v10.2.0.100 (for .NET Framework 1.0).
    Result:
    The application performs as expected.
    My immediate concern is that the client may object to replacing the existing Oracle.DataAccess.dll v10.2.0.100 (for .NET Framework 1.0). What are the best practices for such a situation?

  • Target fieldpoint connection failed due to version conflicts

    I have set up a small network of fieldpoint (fp-2015) and laptop with Ethernet. Then, I have succesfully configured this fp with MAX and downloaded the iak file to it. Now, I want to target the labview RT of this fp. However, the the connection failed with following message "Version Conflicts between host labview and RT Engine". I'm using Labview 7.1 released in August.

    It sounds like the FP-2015 that you have has an older version of software on it (probably LabVIEW 7.0). To upgrade the software on the FP-2015, first launch Measurement & Automation Explorer. Locate the FP-2015 under Remote Systems. Right click on the software item and select Install Software. This will allow you to install the new software image and upgrade the controller to LabVIEW 7.1. Note: You will need FieldPoint Explorer 4.1 which shipped with LabVIEW 7.1. If you have an older version of FieldPoint Explorer, it will not have the 7.1 image for the FieldPoint controller.
    Regards,
    Aaron

  • Does not match component version

    Hi,
    We have four system landscape. We have already upgrade our DEV and ITT to EHP5.We still have to upgrade our UAT and prod to EHP5. When I see the transport queue on ITT system.I see all the transport that was imported on ITT before the upgrade is showing as "Does not match component version".
    I can understand that the version before the upgrade was different so it should show that message.
    I just wanted to check if this is normal or I need to make changes to TMS?
    Regards!
    Ravi

    Hi,
    You can do as follows:
    Switch it off with parameter : SP_TRANS_SYNC = OFF
    Procedure:
    Call transaction STMS
    Goto 'Systems Overview'
    Double click <SID> you wish to add the parameter to
    Goto 'Transport Tool' tab
    Goto 'change mode'
    Add  SP_TRANS_SYNC  to parameter column and OFF to value column
    Save, activate and distribute
    With Version SAP_BASIS 702 a new feature was added to the TMS system,
    tp is now checking the component version of the transport which was
    released and the component version of the system where the transport is
    going to be imported. If there is a difference, this difference is
    highlighted in the import queue (transaction stms_import) and if you try
    to import the transport, the import will stop with a warning message
    about the difference in the SAPCOMPONENT versions.
    If you wish to by-pass with warning then you can choose 'Ignore invalid
    Component version'.
    Regards,
    Aidan

  • Can not view a Software Component Version in Enterprise Services Repository

    Hello,
    I'm trying to import in ESR the software component version created in the SLD. I'm using SAP PI 7.3.
    Into to work area select  Software Component Version and click on checkpoint Import from SLD. Click in bottom Display (List of Software Component Versions) and it show me the list but cannot view the Name of the SWC created.
    I cleared the cache (Environment - clear sld data cache) and the result it's the same, not show the SWC the I created.
    Do you have any idea?
    Thank you in advance.
    --erva

    Hi,
    as it's a new installation, you certainly missed something. have you did controls of Readiness Check doc and tcode SLDCHECK ([see PI 7.1x oss note|https://service.sap.com/sap/support/notes/1143810]).
    and check these post installation controls (but it's for PI 7.1): [http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/60d2a693-9504-2b10-5ba7-82964bd8370e?QuickLink=index&overridelayout=true]
    Mickael

  • Some Software Component Versions do not show up in transaction sproxy

    I have a landscape with a CRM system, a PI system (with the SLD on it) and some other systems.
    In transaction sproxy in the CRM system the Software Component Version SAP CRM ABAP 7.0 shows up, but others that should be there like SAP ABA 7.01 are not there.
    So I went on the SLD and edited the technical system for the CRM system, I added the product SAP CRM 7.00 and set the checkmark for installed for the relevant SWCVs like SAP ABA 7.01.
    I then went to the business system for the relevant CRM client and there also checked those SWCVs.
    But still they do not show up in transaction sproxy in the CRM system.
    What am I missing?

    Hi Monika,
    There's several suggestions that you could look at to help resolve your problem in this thread:
    [Can't find  ESA ECC-SE 603 SWCV;
    Regards, Trevor

  • How to handle Release transfer for Configuration objects in PI 7.1?

    Hello Experts,
    In my current project we are working on Release1 production bug fixing (JDBC to IDoc interface) and parallely on release2 enhancement (field addition, mapping changes)  for the same object.
    I have used release transfer to copy IR objects (mapping, etc) from SWCV 1.0 to SWCV 2.0 and started making Rel2 mapping changes in SWCV 2.0 IR objects. But, am not able to create the ID objects (receiver determination, interface determination, etc) for Rel2 SWCV objects. Even though I select interface from SWCV 2.0, it says object already exists.
    Please suggest.
    Thanks,
    Raks.

    Hi,
        AFAIK ,SWC is not a part of the Key in identifying the receiver determination in the PI 7.1 also....
    which means that no need to create the ID objects again...as said for the changes (sender channel and inbound interface structure...) only change will be in the ESR interface structure.. which will be used by the ID...provided the same namespace is used for the changed message type also....
    Hope this clears you
    Rajesh

Maybe you are looking for