on 01-24-2014 4:23 PM
Hi Experts,
We are working on SRM integration, imported the SRM standard content into ESR which have the standard DT/MT/SI.
Can we import or create the custom objects like DT/MT/MM/SI and OM in ESR under SAP standard namespace.
" http://sap.com/xi/SRM/Procurement/Global "
i have to send the data to third-party web-service. so i have to import the target message structure and do the mapping.
can we do this under the standard content?
Regards
Bhargava krishna
i think you can do that by changing the object property in SWCV defination/
uncheck "object are original objects"
But do remember that it's not a good practise or suggestible to edit the standard content. You can copy them into another SWCV and add the custom content to it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Hareesh,
i don't want to edit anything in standard content.
i just want to import the target structure into standard namespace as external def and create the message mapping/ OM b/w standard DT and the external def.
create service interface for receiver.
so if we uncheck the objects are original objects, we can create them right..
Regards
Bhargava krishna
Bhargava,
Why you dont create a new software compoent at sld and put dependencies of SRM ?
With this process you can edit, without affect the swcv oficial.
I dont recommend you change the objets of stantard SWCV.
Kind regards,
BR.
Ricardo Viana.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Bhargava
you can copy and reuse structure as suggested above , My response was on how to enhance standard content
Can you follow below Article :
You might have to create a new swcv , then create dependency in SLD and regenerate proxy in the backend abap system .
Regards
Srinivas.
Message was edited by: Srinivas S
Hi Bhargava,
Technically you can create object under the standard SAP namespace but it is not good approach. If you update/upgrade the standard content then you can loose your customization in the SWCV.
It is better to copy the object in custom SWCV and use/modify them.
regards,
Harish
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Harish,
thanks for the prompt reply..
i tried by doing that, but when im copying the objects are not copying completely.
because the message type is there in one name space and Data type is there in another namespace.
i copied the MT " Purchase order Request" from" http://sap.com/xi/SRM/Procurement/Global "with all Dependent objects but it have the datatypes in "http://sap.com/xi/SRM/Basis/Global.
Regards
Bhargava krishna
Did you try using the Transfer designed objects feature? That should be easy? under tools
The function "Transfer Object Versions" has the following uses:
a) | You can transfer objects from one software component version (SWCV) to another, for example, to complete the development of one version (of a release) and start a new version (release transfer) |
b) | Transfer objects of a local software component version (SWCV) to a SWCV registered in the System Landscape Directory |
Please check the below link for transfer object detail
Transferring Design Objects - Managing Services in the Enterprise Services Repository - SAP Library
regards,
Harish
Please check the 3rd point in Activity status. the namespace name should be same
Perform the following preparatory steps before executing the release transfer:
...
1. The new software component version that you want to transfer the objects to must be entered in the System Landscape Directory (SLD). SAP software component versions are imported from PPMS. A customer can create his own software component versions in the System Landscape Directory.
2. Import the new software component version into the ES Repository (see: Importing Software Component Versions).
3. To be able to transfer objects to the imported software component version, you must first assign namespaces to it. The namespaces must have the same names as those namespaces from which you want to transfer the objects.
To actually transfer design objects, proceed as follows:
regards,
Harish
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.