SAP release in Adapter

Hi all,
In IDOC adapter if we give higher version than actual version is it give any prob while interface working..
Regards
Rao

Hi
Any incorrect entries here will result in a runtime error.
If you leave this field empty, the last version will always be used.
The Links Expalins this
<b>http://help.sap.com/saphelp_nw04/helpdata/en/96/791c42375d5033e10000000a155106/content.htm</b>
See under Segment version
Thanks
Abhishek Mahajan
*Please Reward points if helpful*

Similar Messages

Step by step procedure to connect SAP XI(Seerburger adapter) wi EDI partner

hi,
I need to know what kind of scenario we have go with seerburger adapter to connect with EDI partner?
give some example scenarios and step by step procedure to connect SAP XI(Seerburger adapter) with EDI partner?
regards
Ruban
Message was edited by:
ruban R

hi,
i found these weblogs,
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
/people/william.li/blog/2006/03/17/how-to-get-started-using-conversion-agent-from-itemfield
/people/paul.medaille/blog/2005/11/17/more-on-the-sap-conversion-agent-by-itemfield
other than any other weblog for this scenario for AS2 adapter for abap proxy to EDI partner to send purchase order ?

Com.sap.aii.messaging.adapter.trans.TransformException:'java.lang.NullPoint

Hi, This is Prasad
We are using 7.0 with SP15, i am using MTB module at receiver side ,we are getting following error.
Message processing failed. Cause: com.sap.aii.messaging.adapter.trans.TransformException: Error converting Message: 'java.lang.NullPointerException'; nested exception caused by: java.lang.NullPointerException
And we are passing following FCC Parameters
Transform.Class = com.sap.aii.messaging.adapter.Conversion
Transform.ContentType = text/xml;charset=utf-8
xml.Record.fieldFixedLengths
xml.Recordset.fieldSeparator
xml.conversionType= StructXML2Plain
xml.recordsetStructure = Recordset,Record
Please help me out ASAP

Hi Stefan,
I am a little bit confused with the parameter "Transform.ContentType".
According to your post it should be "TransformContentType" but the document has not yet been updated. At least when I search within SDN for the document I still get the old version with the dot.
In addition there is OSS note 1131655 from September 2008 (pretty new) and there SAP still refers to parameter "Transform.ContentType".
So, I assume the parameter with the dot is the correct one, right?
Klaus

How to maintain SAP Release status in table COTPL

Hi All,
We have upgraded our system from ECC EHP4 TO ECC EHP 5. Now our SAP Release is 702 but in table COTPL
still the SAP Release status is 701 becuase of which there is error in some of our sap jobs.
Request you all to help us. How we can maintained SAP Release in table COTPL?
Thanks

Hi,
You can try using priority field in the rule. Please check this.
Priority for Responsibilities
If you are using responsibilities for role resolution in Workflow, you can provide individual responsibilities with priorities.
Example: There are various responsibilities for a standard role for processing orders, grouped, for example according to order value (one responsibility for orders up to a certain value, another for orders with a greater order value).
Assuming that orders for a particular customer are always to be processed with the same responsibility (and therefore by the same agent), you can access it via another responsibility with a higher priority that contains the customer name as the only criterion. The responsibility (-ies) with lower priority, and therefore the order value, is then no longer taken into account during agent determination.
Use only numeric values here, and note that, logically, the responsibility with the highest numberic value in this field has the highest priority.
Procedure
1. Sequence Priority of Objects
In Create mode, assign a priority to the objects you wish to rank.
To do so, assign an alphanumeric value (1, 2, 3... or A, B, C...) to each object.
In Change mode, overwrite the value in the field.
2. Priority When Defining Evaluation Paths
In the Priority field, enter the priority or priorities for objects that should be considered in evaluation paths. Enter "*" if you want to have no restriction.
3. Priority for Responsibilities
Maintain the priority directly in the detail screen for the responsibility or in the overview screen for the responsibilities for the rule. Note that you must use numeric values here. On the overview screen, the system sorts the responsibilities in descending order of priority.
Hope this helps.
Feel free to revert back.
-=-Ragu

Please give me parameters of SAP XI HTTP adapter

please give SAP XI HTTP adapter , as i am using this instead of SAP rfc ADAPTER ,
THANKING YOU
SRIDHAR

Hi,
http://help.sap.com/saphelp_nw04/helpdata/en/44/79973cc73af456e10000000a114084/content.htm
Regrds
Chilla..

SAP BC -- SAP XI BC ADAPTER

Hello,
I amtrying to send an ACC_DOCUMENT01 IDOC from SAP BC to SAP XI BC Adapter.
I have done the setup according to the instructions at help.sap.com.
I am hardcoding the XML into the transportservice.
When sending with the Transportservice
pub.sap.transport.XML:OutboundProcess
I get the following error:
Could not run the service 'ACC_DOCUMENT'.
com.wm.pkg.sap.BCException: com.sap.aii.af.ra.ms.api.MessageFormatExcpetion: got no name/namespace for the payload of the XRFC_DOC_TYPE_ENVELOPE: org.xml.sax.SAXException: got no name/namespace for the payload of the XRFC_DOC_TYPE_ENVELOPE
The payload I used
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?> <SAP:IDocOutbound xmlns:SAP="http://sap.com/xi/XI/Message/30"><SAP:TABNAM>EDI_DC40</SAP:TABNAM><SAP:MANDT>100</SAP:MANDT><SAP:DOCREL>640</SAP:DOCREL><SAP:DOCNUM>0000000000002007</SAP:DOCNUM><SAP:DIRECT>2</SAP:DIRECT><SAP:IDOCTYP>ACC_DOCUMENT01</SAP:IDOCTYP><SAP:CIMTYP/><SAP:MESTYP>ACC_DOCUMENT</SAP:MESTYP><SAP:MESCOD/><SAP:MESFCT/><SAP:SNDPOR>SAPXI1</SAP:SNDPOR><SAP:SNDPRN>SE1CLN500</SAP:SNDPRN><SAP:SNDPRT>LS</SAP:SNDPRT><SAP:SNDPFC/><SAP:RCVPOR>SAPSE1</SAP:RCVPOR><SAP:RCVPRN>SE1CLN500</SAP:RCVPRN><SAP:RCVPRT>LS</SAP:RCVPRT><SAP:RCVPFC/><SAP:TEST/><SAP:SERIAL/><SAP:EXPRSS/><SAP:STD/><SAP:STDVRS/><SAP:STATUS>03</SAP:STATUS><SAP:OUTMOD/><SAP:SNDSAD/><SAP:SNDLAD/><SAP:RCVSAD/><SAP:RCVLAD/><SAP:STDMES/><SAP:REFINT/><SAP:REFGRP/><SAP:REFMES/><SAP:CREDAT>2005-10-27</SAP:CREDAT><SAP:CRETIM>19:12:31</SAP:CRETIM><SAP:ARCKEY>                    3D3800D43B140E4AA4E116A43E45F0CF 0000000024373039</SAP:ARCKEY></SAP:IDocOutbound>
Also tried this payload with the same problem
             < sap:Envelope xmlns:sap="urn:sap-com:document:sap" version="1.0">
                < sap:Header xmlns:rfcprop="urn:sap-com:document:sap:rfc:properties">
                  < saptr:From xmlns:saptr="urn:sap-com:document:sap:transport">TREMA100</saptr:From>
                  < saptr:To xmlns:saptr="urn:sap-com:document:sap:transport">DUMMY</saptr:To>
                  < rfcprop:Transaction>TID</rfcprop:Transaction>
                </sap:Header>
                <sap:Body>
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

<SAP:IDocInbound xmlns:SAP="http://sap.com/xi/XI/Message/30">
<SAP:TABNAM>EDI_DC40</SAP:TABNAM>
<SAP:MANDT>500</SAP:MANDT>
<SAP:DOCREL>46C</SAP:DOCREL>
<SAP:DOCNUM>0000000024373039</SAP:DOCNUM>
<SAP:DIRECT>1</SAP:DIRECT>
<SAP:IDOCTYP>ACC_DOCUMENT01</SAP:IDOCTYP>
<SAP:CIMTYP/>
<SAP:MESTYP>ACC_DOCUMENT</SAP:MESTYP>
<SAP:MESCOD/>
<SAP:MESFCT/>
<SAP:SNDPOR>SAPSE1</SAP:SNDPOR>
<SAP:SNDPRN>SE1CLN500</SAP:SNDPRN>
<SAP:SNDPRT>LS</SAP:SNDPRT>
<SAP:SNDPFC/>
<SAP:RCVPOR>XI1CLNT100</SAP:RCVPOR>
<SAP:RCVPRN>XI1CLNT100</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
<SAP:RCVPFC/>
<SAP:TEST/>
<SAP:SERIAL/>
<SAP:EXPRSS/>
<SAP:STD/>
<SAP:STDVRS/>
<SAP:STATUS>30</SAP:STATUS>
<SAP:OUTMOD>2</SAP:OUTMOD>
<SAP:SNDSAD/><SAP:SNDLAD/>
<SAP:RCVSAD/><SAP:RCVLAD/>
<SAP:STDMES>ACC_DO</SAP:STDMES>
<SAP:REFINT/>
<SAP:REFGRP/>
<SAP:REFMES/>
<SAP:CREDAT>2005-10-27</SAP:CREDAT>
<SAP:CRETIM>19:12:30</SAP:CRETIM>
<SAP:ARCKEY/>
</SAP:IDocInbound>
               </sap:Body>
              </sap:Envelope>
Best regards Otto

Hello,
I amtrying to send an ACC_DOCUMENT01 IDOC from SAP BC to SAP XI BC Adapter.
I have done the setup according to the instructions at help.sap.com.
I am hardcoding the XML into the transportservice.
When sending with the Transportservice
pub.sap.transport.XML:OutboundProcess
I get the following error:
Could not run the service 'ACC_DOCUMENT'.
com.wm.pkg.sap.BCException: com.sap.aii.af.ra.ms.api.MessageFormatExcpetion: got no name/namespace for the payload of the XRFC_DOC_TYPE_ENVELOPE: org.xml.sax.SAXException: got no name/namespace for the payload of the XRFC_DOC_TYPE_ENVELOPE
The payload I used
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?> <SAP:IDocOutbound xmlns:SAP="http://sap.com/xi/XI/Message/30"><SAP:TABNAM>EDI_DC40</SAP:TABNAM><SAP:MANDT>100</SAP:MANDT><SAP:DOCREL>640</SAP:DOCREL><SAP:DOCNUM>0000000000002007</SAP:DOCNUM><SAP:DIRECT>2</SAP:DIRECT><SAP:IDOCTYP>ACC_DOCUMENT01</SAP:IDOCTYP><SAP:CIMTYP/><SAP:MESTYP>ACC_DOCUMENT</SAP:MESTYP><SAP:MESCOD/><SAP:MESFCT/><SAP:SNDPOR>SAPXI1</SAP:SNDPOR><SAP:SNDPRN>SE1CLN500</SAP:SNDPRN><SAP:SNDPRT>LS</SAP:SNDPRT><SAP:SNDPFC/><SAP:RCVPOR>SAPSE1</SAP:RCVPOR><SAP:RCVPRN>SE1CLN500</SAP:RCVPRN><SAP:RCVPRT>LS</SAP:RCVPRT><SAP:RCVPFC/><SAP:TEST/><SAP:SERIAL/><SAP:EXPRSS/><SAP:STD/><SAP:STDVRS/><SAP:STATUS>03</SAP:STATUS><SAP:OUTMOD/><SAP:SNDSAD/><SAP:SNDLAD/><SAP:RCVSAD/><SAP:RCVLAD/><SAP:STDMES/><SAP:REFINT/><SAP:REFGRP/><SAP:REFMES/><SAP:CREDAT>2005-10-27</SAP:CREDAT><SAP:CRETIM>19:12:31</SAP:CRETIM><SAP:ARCKEY>                    3D3800D43B140E4AA4E116A43E45F0CF 0000000024373039</SAP:ARCKEY></SAP:IDocOutbound>
Also tried this payload with the same problem
             < sap:Envelope xmlns:sap="urn:sap-com:document:sap" version="1.0">
                < sap:Header xmlns:rfcprop="urn:sap-com:document:sap:rfc:properties">
                  < saptr:From xmlns:saptr="urn:sap-com:document:sap:transport">TREMA100</saptr:From>
                  < saptr:To xmlns:saptr="urn:sap-com:document:sap:transport">DUMMY</saptr:To>
                  < rfcprop:Transaction>TID</rfcprop:Transaction>
                </sap:Header>
                <sap:Body>
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

<SAP:IDocInbound xmlns:SAP="http://sap.com/xi/XI/Message/30">
<SAP:TABNAM>EDI_DC40</SAP:TABNAM>
<SAP:MANDT>500</SAP:MANDT>
<SAP:DOCREL>46C</SAP:DOCREL>
<SAP:DOCNUM>0000000024373039</SAP:DOCNUM>
<SAP:DIRECT>1</SAP:DIRECT>
<SAP:IDOCTYP>ACC_DOCUMENT01</SAP:IDOCTYP>
<SAP:CIMTYP/>
<SAP:MESTYP>ACC_DOCUMENT</SAP:MESTYP>
<SAP:MESCOD/>
<SAP:MESFCT/>
<SAP:SNDPOR>SAPSE1</SAP:SNDPOR>
<SAP:SNDPRN>SE1CLN500</SAP:SNDPRN>
<SAP:SNDPRT>LS</SAP:SNDPRT>
<SAP:SNDPFC/>
<SAP:RCVPOR>XI1CLNT100</SAP:RCVPOR>
<SAP:RCVPRN>XI1CLNT100</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
<SAP:RCVPFC/>
<SAP:TEST/>
<SAP:SERIAL/>
<SAP:EXPRSS/>
<SAP:STD/>
<SAP:STDVRS/>
<SAP:STATUS>30</SAP:STATUS>
<SAP:OUTMOD>2</SAP:OUTMOD>
<SAP:SNDSAD/><SAP:SNDLAD/>
<SAP:RCVSAD/><SAP:RCVLAD/>
<SAP:STDMES>ACC_DO</SAP:STDMES>
<SAP:REFINT/>
<SAP:REFGRP/>
<SAP:REFMES/>
<SAP:CREDAT>2005-10-27</SAP:CREDAT>
<SAP:CRETIM>19:12:30</SAP:CRETIM>
<SAP:ARCKEY/>
</SAP:IDocInbound>
               </sap:Body>
              </sap:Envelope>
Best regards Otto

CIN installation on ECC6 SAP system upgrated from 4.6C SAP release

Hi all,
We have a ECC6 SAP system upgrated 4 years ago from a 4.6C SAP release system. In the old SAP release we don't have installed CIN 40A for India localization, and now we need to have this functionalities has we have to do a rollout on SAP for one indian company.
Problem is that we don't have found any OSS note that explain clearly what we have to do to have in our ECC6 SAP system CIN functionalities.
After application of support packages on level 17 (up minimum required by OSS note 1175384) we have launch function j_1bsa_component_check but we have exception that country IN isn't installed.
We can't use transaction O035 as we have a SAP system already customized.
Thanks in advance for any help or useful information someone can do us about this problem.
Sorry if this couldn't be the right forum to post this type of message, but is't difficult for me, in this particular case, to find the right forum for this type of question.
Regards
Gianpaolo
Edited by: Gianpaolo Papa on Oct 22, 2010 9:55 AM

No asnwers

Jar file containing: com.sap.aii.messaging.adapter.Conversion package??

Hi! Gurus
Can you please let me know the name of the Jar/library file containing com.sap.aii.messaging.adapter.Conversion package.
Your help is greatly appreciated!!
Thank you,
Patrick

> Can you please let me know the name of the Jar/library file containing com.sap.aii.messaging.adapter.Conversion package.
aii_msg_runtime.jar
http://wiki.sdn.sap.com/wiki/display/XI/WheretogetthelibrariesforXI+development

Adding existing RWD uPerform documents using SAP Solution Manager Adapter?

Note# 1468552
Cannot add existing RWD uPerform documents using the SAP Solution Manager Adapter.
Currently, a user can only create a new document with the Solution Manager Adapter; there is no
ability to add existing uPerform documents that have already been created.
RWD has submitted an enhancement to SAP requesting this functionality.
Hi All,
Has there has been any update on the functionality to add existing RWD uPerform documents to Solution Manager? I have found a note from 2010 stating that this functionality has been submitted as a enhancement. My question is, has this feature been implemented yet? If not, does anyone have any suggested work-arounds for this issue?
Thanks in advance!
Stephanie

Hi Stephanie,
I can't find much information on this topic.
You could create a message in component SV-SMG-SPA.
Regards,
Matthew

SAP HCI SFTP Adapter

Hello,
With the SAP HCI SFTP adapter is it possible to connect to an SFTP site that only supports username and password authentication? Do I have to use key based authentication?
Thanks,
Krishneel

Hi Martín
Check this blog. He uses different modules for banking interfaces
http://scn.sap.com/community/pi-and-soa-middleware/blog/2014/04/14/sap-pi-integration-to-different-banks-using-swiftnet-and-bcm
Hope it helps
Regards
Javi

SAP Solution Manager Adapter for SAP Quality Center by HP (ST-QCA)

Hello Folks,
I am configuring Solution Manager, and the current activity asks to download to add-ons that I can't find in the Marketplace - they are required to activate Solution Manager Enhancements:
SAP Solution Manager Adapter for SAP Quality Center by HP (software component: ST-QCA)
SAP Support Enablement package (software component: ST-SEP)
Does anyone know where to get those components?
Thanks a lot,
Marco

Hi Ravindra babu/ Murali:
I have one very quick doubt and would be really glad if you can help clarify.
As per documentation from SAP and also IMG screens etc. it seems like 'a project' in SolMan will hand-shake with 'a project' in QC.
Can I therefore assume that if there is only one instance of SolMan (productive) and one QC server alone (again, productive), any number of trials I carry out between SolMan project and QC project will not spill over into other projects in these two systems and thus have no impact whatsoever at server level.
The reason for my asking this - in my project, Testing has started using QC in a standalone mode already. We have just one server. If I have to carry out any tests/ demo between SolMan and QC, it shouldn't impact other 'standalone' projects being done in QC.
Regards,
Srini

Access BAPIs Using the SAP Java Resource Adapter

Hi experts,
Can someone tell me how to Access BAPIs Using the SAP Java Resource Adapter?

hi Shweta,
Please refer the step by step procedure:
1. Start the deploy tool of the SAP J2EE Application Server with the DeployTool.bat in the directory //<SAP J2EE Engine Installation Directory/.../j2ee/deploying.
2. Choose Project → New Project and enter a name for the new project.
3. Click on the Deployer tab.
4. From the menu path, choose Deploy → EAR → Load Module and select the sapjra.rar file.
5. For the newly created node sapjra.rar, choose Server Settings → Identity Subjects and select Caller Impersonation as authentication type, so that the J2EE user data is used to log on to the ABAP system.
6. Make sure that the J2EE Application Server is running. Connect to the J2EE Application Server with Deploy → Connect.
7. Deploy the sapjra.rar using the menu Deploy → Deployment → Deploy Module.
8. Enter SAPJRADemo as application name and start the application.
9. Close the deploy tool.
10. Start the Visual Administrator again.
11. Select the Cluster tab and switch to <Server Node> → Services → Connector Container.
12. Click on the Runtime tab and choose sap.com/SAPJRADemo → eis/SAPJRADemoFactory.
13. Choose Managed Connection Factory → Properties. On this page, you need to specify the logon data for the ABAP system. There is already some dummy data visible in the property list if no real system data has been specified so far.
14. To change the value of a property, select the property in the list, change the value underneath it, and add the changes using the Add button. At the end, do not forget to save all changes by pressing the button Save Changes. The user configured for the SAP JRA must be the user authorized to read metadata of function modules.

Dynamic coding depending on SAP release

Hello @ll,
I have a program in a 4.7 release where I have to use the OPEN DATASET statement with the addition ENCODING. Now this programm should be transported to a 4.6c release and I get errors because the addition ENCODING is not allowed because it's unknown.
Is it somehow possible to activate resp. deactivate the ENCODING statement depending on the release version? Is there a system field available containing the SAP release version?
Thanks for any help!
C.

You will not be able to deactivate the line of source code depending on release. If you know the target release is 46c and it is coming from 4.7, you would need to have the ENCODING entension in 4.7 and transport it. Mostly likely the activation on the 46c will fail at which point you would need to open that system and manually change that line of code to not have the ENCODING extention. These are the kinds of issues that you will face when transporting between to different releasese.
Regards,
RIch Heilman

SAP Market Place Adapter

Hi Frnds,
What is SAP Market place Adapter, when i refer the doc in help.sap.com, i dint get any idea, in which scenarios we will use SAP Market place.....
Regards,
raj

Hi
You use a marketplace adapter to connect the Integration Server to marketplaces. It enables messages to be exchanged by converting the XI message format to the marketplace format MarketSet Markup Language (MML) and the other way around.
You configure the adapter in the configuration part of the Integration Server when you define a communication channel.
    To be able to send messages from marketplaces to the Integration Server, you must first configure the sender marketplace adapter.
·      To be able to send messages from the Integration Server to marketplaces, you must first configure the receiver marketplace adapter. The receiver adapter supports system acknowledgments but not application acknowledgments.
·        The marketplace adapter takes existing attachments into account and forwards them on.
Configuring the Receiver Marketplace Adapter
http://help.sap.com/saphelp_nw04/helpdata/en/3b/059afabd164c4789075c9810911c14/content.htm
Configuring the Sender Marketplace Adapter
http://help.sap.com/saphelp_nw04/helpdata/en/01/cdd3c885f29247b0bb88d4f9df0b38/content.htm
Thanks
Saiyog

SAP Release details

HI,
Can anybody tel me in which table we can find the SAP release details.
Thank You.
Regards,
Soumya

Navigate deeply through fm STATUS_ANZEIGEN you will get all the below details
Check system variable sy-dbsys for DB name
fm SLIC_GET_LICENCE_DATE for license date
fm SLIC_GET_LICENCE_NUMBER for license number
fm UPG_GET_COMPONENT_RELEASES will get your component releases and the texts from table cvers_txt"<---
DATA: BEGIN OF status_info,
        machinetype(10)    TYPE c,
        system_id(10)      TYPE c,
        database_host      LIKE sy-host,
        database_owner(10) TYPE c,
        database_text(20) TYPE c,
        database_name(10) type c,
        database_release(10),
      END OF status_info.
DATA: BEGIN OF VERSION_INFO OCCURS 0,
          LINE(80),
        END OF VERSION_INFO.
CALL 'SAPCORE' ID 'ID' FIELD 'VERSION'
                ID 'TABLE' FIELD VERSION_INFO-*SYS*.
READ TABLE VERSION_INFO INDEX 3.
STATUS_INFO-MACHINETYPE = VERSION_INFO-LINE+21(10).
READ TABLE VERSION_INFO INDEX 5.
STATUS_INFO-SYSTEM_ID = VERSION_INFO-LINE+21(10).
call function 'DB_DBNAME'
importing dbname = status_info-database_name.
call function 'DB_DBHOST'
importing dbhost = status_info-database_host.
call function 'DB_DBSCHEMA'
importing dbschema = status_info-database_owner.
CALL FUNCTION 'DB_GET_RELEASE'
IMPORTING RELEASE = STATUS_INFO-DATABASE_RELEASE.
*--Server name
call 'C_SAPGPARAM'
    id 'NAME' field 'rdisp/myname'
    id 'VALUE' field servername.

SAP release in Adapter

Similar Messages

Maybe you are looking for