Accessing Sender Agreement details in Module

Hi,
How can we access(read and then modify) the sender agreement details from SOAP header in from ModuleData in the Module interface?
One way I can think of is to read the SOAP message and parse it. The problem lies with accessing the SOAP message in the process method.
I would really appreciate your help.
Thanks.
SK

/people/daniel.graversen/blog/2006/10/05/dynamic-configuration-in-adapter-modules
via that blog you can see how dynamic conf. is done ... via the dynamic conf. you can access mapping runtime too...

Similar Messages

Access Message header details in Adapter module

Hi
I tried to find out solution for accessing sender service and namespace in adapter module...However I couldn't make out correct procedure to access the same. Incase any one aware of accessing sender service details in Module, please let me know...
Thanks a lot...

Hi Yadagiri,
It is possible to acess the Service Name and user Interfaces Please check the API provided for the Module Development.
https://help.sap.com/javadocs/pi/SP3/xpi/index.html
Thanks
Sunil Singh

Problems using access control in sender agreement for SOAP adapter 7.1

I am trying to use Access Control Lists to restrict user access to web services/interfaces which are exposed via PI. This can be configured via the Integration Builder Directory using the u201CAssigned Usersu201D tab of both Communication Components (Business System) and Sender Agreements.
The configuration is via the above mentioned components. However, I understand that itu2019s the adapters which at runtime are responsible for actually applying these checks.
I have been having problems getting the access control to work using a setup involving a SOAP adapter of type SAP BASIS 7.10.
The symptom of the problem is that although the access control works as expected at the Business System level, any settings at the Sender Agreement level appear to have absolutely no effect whatsoever.
I have confirmed that I have no problems if I use an adapter of type SAP BASIS 7.00. However, I really need to get this working on 7.1.
I have looked on the SAP support portal but can not find any notes that relate to this.
Has anyone else had a similar problem? And have you found a fix for it?
Any suggestions would be welcome.
Edited by: Malcolm Dingle on Jun 17, 2009 1:08 PM

Hi Shai,
Please have a look at the following link and see if it helps you .
It deals with SOAP adapter installation and activation
Re: SOAP adapter installation and activation
Best Regards
Edited by: Prakash Bhatia on May 8, 2009 11:51 AM

Problem with Sender Agreement for EDI File to Idoc scenario

I'm configuring PI for EDI with Seeburger Adapter (Calling as a Module) and I'm having an issue with the Sender Agreement using File Adapter.
Process used is File to IDOC. EDI data will be picked up from VAN (Using existing FTP process rather than using Seeburger FTP) and stored in a folder which is being accessed by PI to send to R/3 to create orders.
All my inbound EDI will be stored in same folder which should be picked up by XI and distribute the same depending upon the respective scenario's in ID and respective mapping/config in IR.
The whole process IR & ID works fine and also creates Idoc in R/3, if I configure for one customer for EDI 850, but when I try to configure for second customer for same EDI 850 having same ANSIX12 version (V4010) as previous customer, I get stuck at the Sender Agreement part for this second customer because I use the same CC for File read for both the customers (Scenarios) and since there is a limitation with File Adapter "sender channel must not be assigned to more than one sender agreement ".
How can I create the Sender Agreement using the same CC for my other scenario?
I tried creating multiple CC for different scenario but when I place a test file for customer A, I see that its being picked up by both CC's.
Pl Advise.
Thanks!
PSR

You need to configure splitter as module in sender file adapter (classifier->bic->splitter) as well as define a message splitter(with partner number and Seeburger mapping) in Seeburger workbench.
Thank you for the reply Aamir,
Do you have any document which can guide me through the process?
Does Seeburger Workbench play any role here? because I'm not using See FTP adapter to connect to my VAN. We get the data from the VAN using FTP process but not using See FTP. I'm using BIC to generate an XSD and SDA file, rest everything is in XI using File to idoc and IDOC to file process.
Thx
PSR

Why we do not need sender agreement for Mail and SOAP adapter

Hi SDN,
I know, we do not need sender agreement for IDOC ,HTTP,XI adapters. As these three adapters will run in Integration engine of the abap stack.
In our scenario if sender is other than IDOC or HTTP or XI .
By Refering Sivamni's blog.
/people/siva.maranani/blog/2005/05/25/understanding-message-flow-in-xi
message will be pickedup by communication channel with the help of sender agreement and prepare XI message header by performing cpa cache lookup. then message will go to module processor etc.
In our scenario if sender is IDOC or HTTP or XI .
As these 3 adapters are run in Integration engine.
Doubt 1:
how the integration engine will create the xi message header like sender interface sender system name etc...
Doubt 2:
I believe SOAP and mail adapter will run in adapter engine.but i came to know that we do not need sender agreement and sender comm channel for these two adapters too...then how the XI message header will create...
Please do correct me if i am wrong
and throw some light on the same..
Appreciate your help....
Regards,
Reehan.

Reehan,
Thanks for pointing me to that link. Guess I was wrong .,But,let me try to put to you why you need a sender agreement for a Sender SOAP Adapter,
1. In the sender SOAP adapter , the Sender Interface and the Interface Namespace as provided in the fields Default Interface Name and InterfaceNamespace. The Name of the Sender Service is provided in the WSDL when you ceate the WSDL in the Integration Directory. So, as all details are available in either the Sender SOAP adapter or in the WSDL url you do not need a Sender Agreement. It is not obligatory but you can always create the Sender Agreement.
2. For the mail adapter , if you select the option XIPAYLOAD, you will have the option to mention the Interface Name and Interface Namespace under XI Parameters and so in this case as once again the details provided in the sender agreement are available in the Sender Adapter itself the sender agreement is not needed for the mail adapter when you have select option XIPAYLOAD.
If you have selected XIALL then you need a sender agreement.
Regards
Bhavesh

Please send the details of Notes-note-184754,407485

Hai
Please send the details of Notes-note-184754,407485 to [email protected]
I will assing the points
kumar

Hi check it here.
184754
Summary
Symptom
CAUTION: THIS NOTE WAS REPLACED. FOR MORE UP-TO-DATE, COMPREHENSIVE INFORMATION SEE NOTE 886102.
You want to copy a single BW System of a system group using a database copy. After the copy, you want to have a functional BW source system connection.
Refer to Note 325525. This helps you to select the correct procedure for your scenario. Also note that there are several ways to carry out the actual copy procedure. This is not covered in this note. Refer instead to the URL http://service.sap.com/solutionmanagerbp.
Other terms
Database copy, source system, BW, connection, refresh
Reason and Prerequisites
There are three scenarios:
1. You want to install a new BW (referred to below as "target BW") by copying an existing BW (referred to below as "original BW"). That is, you import the copy onto an empty computer.
2. You want to replace an existing BW (henceforth "old BW"), by copying a different BW (henceforth "original BW"). That is, a BW was already installed on the target host (the old BW). We will call the copy of the original BW "target BW". There are two different scenarios here:
a) You are still in the planning phase of this step, that is, you have not yet made the copy.
b) You have already overwritten the old BW with the copy of the other BW.
Solution
You must perform ONLY THE STEPS required for YOUR SCENARIO.
Scenario 1): In 1.2B, create a transport request in the original BW that contains all source system-dependent objects for all R/3 and DataMart source systems. The object types are ISMT, ISTT and ISTS. Note that the ISTS object (the transfer structure) may contain routines that must be transported as separate objects (Object Type ROUT).
As of BW 2. 0A, you are supported by the BW transport link, grouping "Backup for system copy". Select the R/3 and DataMart source systems in the source system filter and collect the source systems using the Drag and Drop function.
If you use type PSADELETE processes, also add these to the transport request.
Scenario 2)a): Create the described transport request in the old BW.
Scenario 2)a): In the old BW, delete all R/3 and DataMart source systems in the Administrator Workbench source system tree.
Scenario 1), 2)a) and 2)b): Import the copy.
Scenario 1), 2)a) and 2)b): In the target BW, change the contents of the "target host" field in all RFC connections (destinations) for R/3 and DataMart source systems (Transaction SM59) to a nonsensical, nonexistent address (such as 'nowhere'). Then, delete ALL R/3 and DataMart source systems in the Administrator Workbench source system tree. Caution: This step deletes all PSA tables of these source systems - the data is lost. A message is generated stating that the source system cannot be accessed (since you deleted the host of the RFC connection). Select "Ignore".
Scenario 2)b): Change to the source systems connected to the old BW and THERE delete the connection (in the source system) to BW. To do this, change to Transaction SE37 - RSAP_BIW_DISCONNECT function module Sngl. test. Parameter I_BIW_LOGSYS = <name of BW>, I_OLTP_LOGSYS = <name of the source system>, I_FORCE_DELETE = 'X'.
Scenario 1): If you want to connect the target BW to one or more source systems that are also connected to the original BW, assign a new logical system name (Table T000) to the target BW. However, we recommend that you follow Note 184447 when designing the system environment.
Scenario 2)a) and 2)b): Assign the same name to the target BW system that was assigned to the old BW system (logical system name, Table T000).
Scenario 1), 2)a) and 2)b): If you have just renamed the BW, execute Transaction BDLS to convert all relevant tables to the new logical system name. To do this, refer to Notes 121163 and 369758.
Scenario 1): Connect the required source systems. (Administrator Workbench - Source systems)
Scenario 2)a) and 2)b): Connect the source systems, that were connected to the old BW. (Administrator Workbench - Source systems)
Scenario 1) and 2)a): Import the request created above. Bear in mind the special CTS features for the source system-dependent objects (system changeability in connected systems; View V_RSLOGSYSMAP).
Scenario 2)b): Recreate the transfer structures/transfer rules and activate them.
Header Data
Release Status: Released for Customer
Released on: 20.03.2007 15:58:10
Priority: Correction with medium priority
Category: Consulting
Primary Component: BW-WHM-DST-SRC Source Systems
Releases
Release Independant
Related Notes
886102 - System Landscape Copy for SAP BW 2.X, 3.X and NW2004s BI
733623 - Oracle export/import for BW system copies
524554 - Storing destinations in the BW environment
369758 - BDLS: New functions and better performance
325525 - Copying and renaming systems in a BW environment
127326 - CTS for InfoSources, update rules ...
121163 - BDLS: Converting logical system names

40785
Summary
Symptom
You are transporting BW objects that are heavily linked with each other so that several requests are necessary.Objects of a request are using objects which are locked on other requests.
In the target system, errors arise during the method execution of requests with BW objects (return code 8).The messages indicate that objects are required which do not exist in the target system and are also not contained on the request.
For example, you transport an object with attributes, but the attributes are not transported nor are they available in the system.In the log, message R7322 appears: 'Attribute &1 from characteristic &2 not (actively) available'. As a result, an InfoCube cannot be activated if InfoObjects are missing and so forth.
Additional key words
CTS, transport link, AWB, object collector
Cause and prerequisites
You collect objects with the transport link of the Administrator Workbench and then write these to a transport request.In the process, all objects which have not yet been transported are marked (development class $TMP). Or you install Business Content and write the installed objects directly to a request.
Objects with a different development class (not $TMP) are also gathered but they are not marked because the system assumes that these have already been transported and are then subject to automatic recording.If you are not sure whether these objects already exist in the target system, you can mark the objects.The system then writes them to the request and transports them (once again).
It could happen that objects that are locked on another request have been collected.You can recognize this by the column "Transport request" in the window with the collected objects (you may have to expand the tree with the collected objects completely). You should always release the requests beforehand, that means prior to the request that is being compiled.
This is because these objects are needed by objects that the system is now collecting, but do not yet reside in the target system or do not yet reside there in their most current version. If you import the request which the system is collecting prior to the other request, then the errors described in the symptom section of this note.
Solution
Proceed as follows if you are using the object collector:
Collect the objects
expand the tree with the collected objects completely
Release all requests that are displayed in the 'transport request' column.
Only then release the request with the objects that are being currently collected.
As of Support Package 16 this approach is simplified even further.In this case, a log with the following messages is displayed after writing the collected objects:
'Objects which are locked on a different transport request' (Message RS0305).If you expand this message, you receive a list of all objects which are locked on other requests.
'Transport requests which must be released first' (Message RS0306).If you expand this message, you receive a clear summary of the requests which must be released before the request currently being compiled.Here the system simply summarizes the requests from the previous list that still contain dependent objects.
Thus, as of Support Package 16 you no longer have to expand the tree completely and search for linked requests.
Source code corrections
Header Data
Release Status: Released for Customer
Released on: 05.09.2001 22:00:00
Priority: Recommendations/additional info
Category: Consulting
Primary Component: BW-SYS Basis System and Installation
Secondary Components: BW-BEX Business Explorer
BW-WHM Data Warehouse Management
Releases
Release Independant
Highest Implemented Support Package
Support
Packages Release Package
Name
SAP_BW 20B SAPKW20B19
SAP_BW 20B SAPKW20B20
Related Notes
125499 - Activation error after transport of BW objects

What's the usage for WSDL of sender agreement?

Hi gurus,
Our scenarios are using soap sender adpater, and we find in PI 7.11 there is a functionality to display the wsdl of sender agreement.
It seems xmlspy can create soap request based on the url format of wsdl, but we can't send the soap request to PI as it gave the error message as below " Couldn't retrieve inbound binding for the given P/S/A values: FP=;TP=;FS=null;TS=;AN=null;ANS=null;".
Do we have to use the "TOOLS->display wsdl" menu to get the wsdl file to local and then provide it to 3rd party system? If so, we have to export wsdl again whenever data structure changes.
Thanks in advance.

HI,
Do we have to use the "TOOLS->display wsdl" menu to get the wsdl file to local and then provide it to 3rd party system? If so, we have to export wsdl again whenever data structure changes.
---->yes ,we have to export wsdl again whenever data structure changes.
and
we have 2 approaches for generating WSDL FILE
1. in sender Agreement
2. from memu bar-> tools
but we have to generate WSDL file Through Menu bar "TOOLS" because there is chance to provide url and sender details after change the Structure..,..
thanks,

Why we dont need sender agreement and comm channel in IDOC to file scenario

Hi,
there are 2 queries:
first query :
Scenario is "Idoc to file transfer"
why we dont need sender agreement and communication channel for IDOC to file ,while we do need
both of these for "File to RFC "
Answer : which i got is because IDOC sits at ABAP stack but same is valid for RFC also.
Then why For "IDOC to file" we dont need that.
Second query:
Also when i did scenario for File1-RFC-File2 scenario using BPM i have created a interface
between XI-RFC synchronous to send data which we got from file1 in XI to RFC importing parameter
and getting data from RFC back to File2.
Here in IDOC to file scenario why we dont need any interfface for IDOC-XI Asynchronous.
Regards,
Mayank
Edited by: mayank verdia on Jan 13, 2009 11:49 AM
Edited by: mayank verdia on Jan 13, 2009 11:50 AM

Dear All,
For file to idoc scenario is there any possibility to get line items details or xml details i.e the segments and its related field details using reference id, transaction id or interface name or message id in SAP PI 7.0. I know we need to click each and every message in sxi_monitor and look for details.
For SAP(R3 System) I can create a report and set the job for specific time period so automatically it throws the details(like reference no, document date, invoice no from) in ftp path as .csv file. The same ftp path is maintained in program.
I wanted to check FTP--->PI postings and I have set the job at r3 system it is working fine and Im monitoring it too.
Now the end to end scenario is FTP--->PI--->ECC(R3 system). Please help.Many Thanks.

How to configure MS-Access 2010 DB details on weblogc using DBAdapter

Hi Experts,
Can any one help me how to configure MS-Access 2010 DB details on weblogic 11g using DBAdapters.
If you provide step by step instuction, it is very usful to me.
If you have any screen shots you can any one please send a file to my mail ID:[email protected]
My Requirement:
I need to fetch 3 columns data (product code/ serial numer and serial status) from MS-Access 2010 and store it on oracle 11g, for that I have wrote a web service code and I need to make it automation. I don't have any IDEA, how to make this web serevice as automation (automation means, when ever new record stored in MS-Access data I need to fetch newly created record from MS-Access 2010 and send it to Oracle 11g)
Note: MS- Access 2010 present at vision system and Oracle 11g installed in linux server.
Thanks,
Phani

Hi,
I am also facing the same issue, not sure about what url to use. And also the login webservice doesn't work while I am testing using http://localhost:81/RTC/RTCService.asmx. It always throwing the following error
" Unable to cast COM object of type 'RTCLib.RTCClientClass' to interface type 'RTCLib.IRTCClient'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{07829E45-9A34-408E-A011-BDDF13487CD1}' failed due to the following error: No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE))."
Is the current owc_lcs.zip support MS Office Communication Server 2007?
Please share the configuration step if anyone already integrated OCS 2007.
Thanks,
-Mukesh.
Edited by: user9127933 on Feb 19, 2010 4:05 AM

Wrong Sender Agreement:The Sender agreement does not have channel

Hi Guys,
I am trying RFC to File scenarion where I am triggering a report which is calling a RFC module I have given the destinaztion name correct .When I am executing the report it is failing giving the following error
"Wrong Sender Agreement:The Sender agreement does not have channel"
I have checked that sender agreement is there.
Also when Iam changing the RFC call by removing IMPORTING parameters and adding IN BACKGROUND TASK It is getting executed and goin to XI successfullly but after adding IMPORTING Param it is failing ?
Any suggestion on the same?
Regards

Hi Guys ,
I have tested the same again from RFC directly without Report and after some time it failed giving 'SYSTEM ERROR'.
When i checked the channel it is giving following error:
Error: 2008-01-10 13:36:19 IST: Message processed for interface Z_RFC_TESTSYNCASYNC: com.sap.aii.af.mp.module.ModuleException: call to messaging system failed: com.sap.aii.af.ra.ms.api.DeliveryException: Received HTTP response code 500 : Timeout caused by: com.sap.aii.af.ra.ms.api.DeliveryException: Received HTTP response code 500 : Timeout
Any help now ?
Regards

No suitable sender agreement found - File / Adapter, Sender FTP

Hi SDN Friends,
Is my first time in PI with FTP / FILE ( really I'm newbie in PI - but 2 years in ABAP ).
I have configurated my communication channel with and FILE/ADAPTER on a Sender FTP...
I have Tried with 2 FTP, one in my PC, and one Public... but in both cases, it's doesn't works... monitoring my communication channel, I get the No suitable sender agreement found ERROR....
I thought... may be PI has not access to the FTP's servers, so run in SAP PI server, an ABAP program trx se38, program: RSFTP002 and with this, I could connect to the FTP... it works perfectly.
so I don't understand... what I'm doing bad?
Any Help?
regards every body!

u r welcome...2 yrs back i am newbie
when ever we make changes after an error, sometimes XI will not take the changes in cache automatically; uses old one. solution for this is complete Cache refresh.
welcome to Integration World have fun....

Sender Agreement Determination Error

Hi Experts,
I am getting an error while posting my message from RWB. the error details is below.
Error While Sending Message: 500 Error during Sender Agreement Determination
It is a HTTP to IDOC scenario so no need to determine the sender comm channel and sender agreement, so I have not done that
but still the error persists. Please help me out. As, everything seems ok to me.
Thanks and regards,
Aniruddha

Hi,
If any ABAP Adapter is tested ideally if u post directly to IE it sholuld not through a error.
Please check if u have any other interface with the same name and same BS, but have 1 sender agrement.
If yes try to rename any1 of the two.
Also refresh the once and try to test it again
Babu

Certificates are not listed in Sender Agreement

Hi,
I have a message level key pair created on an adpater engine(say, ABC) under a Keystore view of type "USER". On target PI( where i am configuring to recieve the message from a source PI), I have a sender agreement where in i am decrypting the message using the key created on adapter engine(This adapter engine is not a center adapter engine. Its a deifferent server than the targer PI).
In the SOAP sender adapter channel i have selected adapter engine as ABC instead of centre adapter engine. And the same SOAP sender channel is used in Sender agreement.
When i am trying to put the certificate details in sender agreement with the F4 help, certificates that i have created on ABC are not listed on target PI. Other certificates(under keystore view of type "System") are listed.
What could be the problem here?

Hi,
I think the problem is due to corresponding certifice wrongly add to list in visual administrator, generally keystoreentry and keystore view etc lists available. Better to check with basis team your required certificate was added to which list. Some time the problem is due to inside certificate data also for the check with certificate people they will sort out easily.
I have faced same problem in one of my project, i have raised question to sap. They have suggested below ways to sort out problem
the F4 help of the Integration directory will not recognize the
Certificate if the Subjectkeyidentifier field of the certificate is leftunfilled . The issue can be dealt with in 3 different ways .
1. Type in the Certificate name with out the use of F4 help (OR)
2. Regenerate the certificate with a valid value for the
subjectkeyidentifier . (OR)
3. Edit the adapter meta data which is present in the Integration
repository and get the F4 help working .
For this,remove the following tag from the adapter meta data file
<HelpServiceQueryAttribute>
<Name>X509Extension</Name>
<Value>SubjectKeyIdentifier</Value>
</HelpServiceQueryAttribute>
This will be inside the <HelpServiceQueryAttributes> tag .
This method has the disadvantage that any upgrade will result in the adapter metadata being overwritten and hence the above change will
be reverted.

Sender agreement & communication channel not needed in case of IDOC adapter

Hello everyone ,
I am new to xi , as far as i know a communication channel cannot be created in ID when using IDOC adapter , the answer for this question is like , the idoc adapter resides on the integration server & not part of j2ee AF .
Can some one explain me in the terms of a laymen , its not clear to me.
Thanks & Regards,
Reena.

Hi ! Reena
IDOC adapter resides on Integration server, so Integration engine takes care of the conversion format from IDOC to XML, hence there is no need for sender Adapter .Also since its residing on Integration server you can directly post the message in the Integration engine.
well lemme explain a little bit,the main reason for sender agreement is to associate namespace with the sender adapter,now when we shoot IDOC from R/3 it already contains its standard SAP namespace so no need of sender agreement.
now comes the sender CC,main use of sender CC is to identify the sending system and the adapter.the IDOC header contains details of all the this,so again there is no need for sender CC
loook at this thread discuss the same
Re: Why we r not Creating Sender Agreement For HTTP & IDOc Adapter at Sende
Re: why HTTP & IDOC adapter do not require sender communication channel?
Thanks!!
Questions are welcome here!!
Also mark helpful answers by rewarding points
Regards
Abhishek Agrahari

Sender Uses Virtual Receiver - Receiver Determination & Sender Agreement

Hello all,
There is a Checkbox with Sender Uses Virtual Receiver while creating Receiver Determination & Sender Agreement.Could anyone tell when one shall use that checkbox & diffrence of using the same in Rx Determination & Sender agreement ? And Lastly What is the significance of using * in Party &
Service in that Sender Uses Virtual Receiver part ?

Hi,
we will use it when we are using B2B scenario......
More details... please check this.............
/people/shabarish.vijayakumar/blog/2008/09/16/virtual-receiver--why-do-you-really-need-it
https://www.sdn.sap.com/irj/scn/wiki?path=/display/xi/virtual%252breceiver%252buse%252bin%252breceiver%252bdetermination%252bb2b(Idoc%252bto%252b(File%252cIdoc%252bor%252bany%252bother%252bsystem))
http://help.sap.com/saphelp_nw04/helpdata/en/b1/f29e7a56e18a439984a3c6630951d2/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/26/5ccd3bb4560f01e10000000a11402f/frameset.htm
http://help.sap.com/saphelp_nwpi711/helpdata/en/48/ce2a423a8e5430e10000000a42189b/content.htm
Thanks

Accessing Sender Agreement details in Module

Similar Messages

Maybe you are looking for