In Adapter, MODULE tab, there is CallSAPAdapter : What is that?

In most of my Communication Channel (adpater configuration) in IB Directory,
under the MODULE tab, there is CallSAPAdapter (Local Enterprise Bean),
what does it actually mean,
I tried removinf it from the sender channel, and the scenario was working as well,
but i dont what role it plays in the sender and receiver channel

Hi,
We use the module porcessor to specify generic module that give Adapter extra functionality.
Some standard module are default provided by sap each of then for diff purpose.
PayloadSwapBean : You can swap the main payload of the XI message with another payload of the message that is an attachment
StrictXml2PlainBean:You can convert an XML document in the main payload of the XI message to text format
XMLAnonymizerBean: You can anonymize XML elements and attributes.
PayloadZipBean:You can compress one or more payloads or extract payloads from a compressed file.
TextCodepageConversionBean:You can swap the code page of the main payload of the XI message and convert the content using the new code page.
DynamicConfigurationBean:You can edit the message header for adapter-specific message attributes.
MessageTransformBean, Migrating Dispatcher Classes
Apart from these you can develop ypur own adapter modules depending on the requirement.
This blog will give you a clear picture.
/people/stefan.grube/blog/2007/02/20/working-with-the-payloadzipbean-module-of-the-xi-adapter-framework
Cheers,
*RAJ*

Similar Messages

AS2 adapter-- Module tab configuration to call seeburger std mappings..!

Hi Experts,
Seeburger has been installed and i want to use AS2 adapter to make use the seeburger standard mappings.
When i opened the module tab, its been found that for
Sender AS2 adapter:
Module Name                                     Module Key
localejbs/Seeburger/solution/as2             solutionid
localejbs/CallSapAdapter                         exit
Module configuration
_Modulekey      ParameterName               ParameterValue_
Solutionid           Mappingname               SEE_ORDERS_UN_...
can i use the above steps??
Is solutionid is enough to call the seeburger mapping?
or
do i need to use the Bic module to call the seeburger std mapping like below?
Module Name                                    Module Key
localjbs/CallBicXIRaBean                         bic
Module configuration
Modulekey     ParameterName               Parameter Value
Bic               Mappingname              SEE_ORDERS_UN_...
Kindly let me know.
Regards
Krupa.

HI,
For module configuration for As2 refer the below help.
Sender configuration:
AS2 identifier is the party identified which will be provided by the WAN network provider.
Under the party identifiere tab
Agency will be seeburger
Scheme=AS2ID
Name = WAN network no of the partner who is sending the file
Few changes in the module parameter tab.
localejbs/CallBicXIRaBean bic
CallSapAdapter 0
Module configuration:
bic= destSourceMsg = MainDocument
bic= destTargetMsg = MainDocument
bic= mappingName= See_E2X_EDIFACT_ORDERS_UN_D93A
Receiver AS2 adapter configuration:
When the adapter is used in a receiver channel, it obtains a message from the Integration Engine and sends it to a business partner. In this case, the following steps are required:
1. Define the channel as a Receiver channel on the Parameters tab
2. The last step ensures the module sequence is complete:
Make sure the module ModuleProcessorExitBean does exist in the module sequence:
Module Name=localejbs/ModuleProcessorExitBean
Type=L
Module Key=Exit
with the following module parameter:
Module Key=Exit
Parameter Name=JNDIName
Parameter Value=deployedAdapters/SeeXIAS2/shareable/SeeXIAS2
Refer the below thread which has the same discussion.
Re: Pls.. Help Needed.. Seeburger Mapping Names..!!
Thanks and Regrds,
Chirag

Up by the tabs there is a search feature that I dont know if it is suppose to be there

I can't add a picture but if I could I would that might be more helpful. It has an i next to it and when you click it says updated search bar.

That was it the default search bar. Thank You for the quick reply.

How to test Adapter Module

Hi
My Scenario is File - to - File
I have written one adapter module and i have deployed in J2ee Engine as well. In sender communication channel i have given the JNDI name like
"localejbs/<JNDI Name>".I have tested the my file to file scenario by placing a file in source directory which i have mentioned in Communication channel Source Directory and File Name.But i didnt find any difference in target file.
I have used the following blog

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/da5675d1-0301-0010-9584-f6cb18c04805
1.How to test the adapter module.
2.How to configure my communication channel.
Please help me its very urgent
Best Regards
Ravi Shankar B

Hi,
check JNDI service in visual admin to see if
your service has the same name there
>>>>1.How to test the adapter module.
by using it in a channel
>>>>2.How to configure my communication channel.
add you adapter module to the adapter module tab
in communication channel
Regards,
michal

Required JAR's for developing custom adapter modules for PI 7.31 SP 09

Hello experts,
I have a new development wherein i have to consume .xlsx files in PI 7.31
i have gone through a lot of blogs but did not find any relevant JAR's specially for PI 7.31, I am planning to go for custom module development for conversion of .xlsx file into xml
so need your help for finding the JAR's for PI 7.31 and also some custom JAVA source code for conversion of excel spreadsheet into XML.
Regards,
Sushant.Shinde

Hi sushant,
The module key seems correct ffor you. But the blog you shared is cozy. I developed 4 adapter modules using a document. Please refer that.
And NWDS EHP1 is available you can use that to be perfectly sure on compatibility.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c0b39e65-981e-2b10-1c9c-fc3f8e6747fa?overridelayout=true
use the above document to verify the steps you followed-
Please provide following screenshots
NWA->configuration->infrastructure->Application Modules-> and search for *xlmodule*
if you find your module then click on it and at the bottom there will be a window with JNDI Name. Share that JNDI name and use that JNDI name in your Module. (localejbs/JNDIName).
Also go to NWA->TroubleShooting-> JNDI Browser and see where is your Adapter module situated. I mean under which directory. Either directly inside root/localejbs/ or root/localejbs/sap.com.
Please verify your steps according to that and redeploy and share result.
and Go to NWA- Site Map-> find Start & Stop
In that go to Java Applicaitons Tab and search for your module. It must be started. If it is stopped try starting it.
Regards,
Vikas

Adapter Module Vs Function Module

We are creating a Adapter Module to process an Incoming File. The File contains the Material Master data. But there are many records are invalid due to various reasons. We need to strip the badrecords.
There are around 650 fields in each record and the condition are very complex to be validated in the XI message mapping. Thats were we decided to go with an Adapter Module.
But my question here is, can i write a Function Module in XI and send the File to the Function Module to validate them and there by strip the bad records, rather than writing an adapter module?
Any Suggestions

Hi Jenni,
I assume that, you are an ABAPer and you do not want to go for an adapter module creation. My suggession would be -
Use the file adapter. use FCC and create the XML structure you need. Do not have any validations at this time. Just create the XML. Now you have two options -
a. Create an ABAP mapping and pass this XML to the ABAP mapping. Implement all of you business validation rules here, and create the target structures only when everything looks good. Here you would have full control over the target message.
b. If you are more interested in writing a FM. creating a function module (rather server synchronous proxy) then implement the logic here. The output structure of this proxy would be with all the good records. You would need to have BPM in this case.
I beleive I made some sense.
VJ

Deployment of Adapter Modules.

Hi,
Do we deploy the Adapter Modules using SDM.
In that case how do we assign that o the specific communication channel.
If i dont assign will they work?
Thanks in Advance.
Raj

>>Do we deploy the Adapter Modules using SDM.
Yes.
>>In that case how do we assign that the specific communication channel.
Specify the adapter module under the Processing Sequence of Module tab in the CC.
>>If i dont assign will they work?
No. It will not work.
Thanks
SaNv...

How many types of function modules are there

hi gurus,
how many types of function modules are there...
what type of function module bapi is....
i don't know much about that...
pls help me...
regards,
praveen

hi
hope it will help you.
<REMOVED BY MODERATOR>
Function Modules Used in Script:
In the Driver Program we must use all or some of the function modules that are listed below to transfer the data.
Open_Form
Close_Form
Start_Form
Write_Form
Write_Form_Lines
End_Form
Control_Form
Read_Form_elements
Read_Form_Lines
Any driver program must contain Open_Form, Close_Form and Write_Form. Other function modules are optional.
OPEN_FORM: This function module opens layout set printing. One must call this function module before he uses any of other layout set function modules like Write_Form, Start_Form, Control_Form etc., You need specify a layout set name in the export parameters of this function module. If nothing is passed to Open_Form then one should use Start_Form function module to open layout set before starting the output. The layout set opened by Open_Form should be closed by Close_Form function module, other wise output doesnt appear. We can use any number of Open_Form, Close_Form functions in one single program. But Close_Form must be there for every Open_Form in the program.
Some of the important export parameters we have to pass to Open_Form function module.
Form: Enter the Layout set name here, which then controls the output formatting. If nothing is specified then we must use Start_Form for opening layout set.
Language: Layout sets are Language dependent. Enter the desired language here. If the entered layout set is not in that language, then the function tries to open the Form entered in its original language. The default value is SY-LANGU.
Device: SAP Script can format a text on different device types. The device can be PRINTER or TELEX, TELEFAX, ABAP and SCREEN.
Dialog: Use parameter DIALOG to determine whether to display a dialog box before printing, in which the user can set several spool parameters for print formatting. Possible values: SPACE displays no print parameter screen. 'X' display print parameter screen. Default value: 'X'
Options: Use parameter OPTIONS to set several options for print formatting. The parameter has the structure ITCPO. The user can change some of the defined settings on the print control screen. The default value for Options is . We will discuss about ITCPO structure in detail later.
Other Export, Import and Exceptions are self-explanatory.
Close_Form: The function module closes the layout set opened using OPEN_FORM. The system executes any terminating processing steps for the last opened layout set. No Export parameters for this Function Module.
Start_Form: In-between the function modules OPEN_FORM and CLOSE_FORM, we can use different layout sets. This allows us to combine several different layout sets into one print output. However, we can combine only those layout sets that have the same page format. To switch layout sets, use the function module START_FORM. If another layout set is still open, we must close it first using END_FORM. If we specify no layout set name when calling START_FORM, the system restarts the last open layout set. If after OPEN_FORM no layout set was activated yet, the system leaves the function module with the exception UNUSED. Some of the important export parameters for this function module are
Form: The parameter contains the name of the layout set you want to use for printing. If you specify no layout set here, the system restarts the last active layout set.
Language: Layout sets are language-dependent. Enter the desired language here. If the layout set does not exist in this language, the system tries to call the layout set in its original language. If the parameter LANGUAGE is empty, the system uses the language of the last active layout set.
Startpage: Usually, SAP script starts with the page specified as start page in the layout set definition. If we want to start output with another layout set page, enter the name of the desired layout set page here. If the desired page is not defined, the system uses the start page defined in the layout set.
Program: To replace program symbols, SAP script must know which active program contains the work areas for the values to be passed. If we omit the parameter, the system searches for the field values in the program that was specified in the parameter OPTIONS (field TDPROGRAM) of OPEN_FORM. If we enter a program name, the system replaces the program symbols with the values from this program up to the next END_FORM.
Exceptions and other Export, Import parameters are self-explanatory.
Write_Form: The system outputs the layout set element specified in parameter ELEMENT into the currently opened layout set. In the parameter WINDOW we can specify the name of a window for the output. Remember that the layout set element must be defined in this window. The parameter FUNCTION specifies how to merge the text lines to be output with any existing contents in the window. In this case, there are differences between the different window types or areas. Some of the important export parameters used in Write_Form.
Element: Specify the name of the text element you want to output into the layout set window specified in the parameter WINDOW. The element must be defined in that layout set window. If you specify no element, the system uses the default element, if one is defined in the layout set.
Window: Specify the name of the window into which you want to output the layout set element specified in the parameter ELEMENT. Default value for Window is MAIN.
Function: The parameter determines how to output the text element into the respective window. The output type depends on the window type and area:
Window Type: MAIN Area: BODY
SET/APPEND: Appends to previous output.
Window Type: Main Area: Top/Bottom and
Window Type: Other than Main and all areas
SET : Delete the old element contents and prints the new elements
APPEND: Appends the new content to existing elements.
Type: The system interprets this parameter only for output to the main window. The parameter determines the area of the main window into which we want to output the element. Possible values: 'TOP' header area
'BODY' main area
'BOTTOM' footer area
Default value: 'BODY'
Write_Form_Lines: This function module outputs the text lines in table LINES into the specified layout set window. The text lines must have the SAP script ITF format. From the data in the text header, the system uses only the field TDSTYLE to apply the formatting attributes defined in the specified style for this text. If the field is empty, the system uses the identically named formatting attributes (character and paragraph formats) of the layout set.
Use parameter WINDOW to specify into which of the windows defined in the layout set we want to output the text. We can specify any window used in the layout set. The parameter FUNCTION determines how to merge the text lines to be output with any existing contents in the window. There are differences between the different window types or areas.
Header: This parameter contains the header of the text module we want to output in the current layout set. For the formatting process, the system uses only the entries in the header fields TDSTYLE and TDFORM. Structure: THEAD
WINDOW: Enter the name of the window into which we want to output the layout set element specified in parameter ELEMENT. Default value: 'MAIN'
FUNCTION: This parameter determines how to output the text element into the respective window. The output type depends on the window type and area: Window type MAIN, area BODY: 'SET' append to previous output 'APPEND' same as SET. DELETE' no effect. Window type MAIN, areas TOP and BOTTOM; all other windows: 'SET' delete old window or area contents and output the element 'APPEND' append the element to the existing elements 'DELETE' no effect Default value: 'SET'
TYPE: The system interprets this parameter only for output to the main window. The parameter determines the area of the main window into which you want to output the element. Possible values: 'TOP' header area 'BODY' main area 'BOTTOM' footer area Default value: 'BODY'
END_FORM: END_FORM ends the currently open layout set and executes the required termination processing. After calling this function module, no more layout set is active. For further output, we must start a new layout set using START_FORM. No Export parameters.
CONTROL_FORM: Use this function module to pass SAP Script Control Commands to the layout set. The Control command is passed through the export parameter COMMAND in quotes.
READ_FORM_ELEMENTS: This function module fills a table with all text elements that appear in one layout set. If we specify no layout set name, the system includes all elements of the currently open layout set. If we specify a layout set, the system uses the information about the active version of the layout set, retrieved from the database. Here we have two export parameters, Form and Language and a table parameter Elements.
READ_FORM_LINES: Use this function module to transfer the lines of a layout set element into an internal table. If we specify no layout set name, the system transfers the text lines of the currently open layout set. If we specify a layout set, the system uses the text lines of the active version of the layout set from the database. The Export parameters are Form, Language, Window and Element. If we pass these 4 parameters the function module returns a table with the lines from layout set.
Function modules are one element. There are no types. However sometimes an RFC enabled function module is referred to as RFC Function module, but really it is just a function module. Also BAPIs are function modules, but are usually referred to as just BAPI as opposed to BAPI Function module.
There is no different function module types , but calling the function module will be different.
check this function calls syntax
1. Calls a function module:
CALL FUNCTION func.
2. Call a function module in a different mode (asynchronous Remote Function Call):
CALL FUNCTION func STARTING NEW TASK taskname.
3. Call a function module in the update task:
CALL FUNCTION func IN UPDATE TASK.
4. Call a function module in a remote system (Remote Function Call, RFC ):
CALL FUNCTION func DESTINATION dest.
5. Asynchronous call to a function module with transactional processing (transactional Remote Function Call):
CALL FUNCTION func IN BACKGROUND TASK.
qRFC with output queue
6. Call a function module that can be activated in the context of enhancements:
CALL CUSTOMER-FUNCTION func.
Cheers,
Chandru
Edited by: Alvaro Tejada Galindo on Feb 27, 2008 11:53 AM

Regarding Adapter Module in XI..

Guys,
Anybody let me know the step of step procedure of implmenting custom adapter module in XI...
So that i can implement by following steps..
Somu.

Hi
Adding Wiki as well
https://www.sdn.sap.com/irj/scn/wiki?path=/display/snippets/write%252bpayload%252bto%252ba%252bfile%252bfrom%252badapter%252bmodule
https://www.sdn.sap.com/irj/scn/wiki?path=/display/snippets/change%252bpayload%252bin%252badapter%252bmodule
These all are advance concepts.
I think the basic adapter module guide you should try first
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e21106cc-0c01-0010-db95-dbfc0ffd83b3
Thanks
Gaurav

Does the 'CallSapAdapter' adapter module perform the FCC?

Hello,
I have a scenarion where
Step 1 - An encrypted file has to be picked by the sender file channel
Step 2 - It has to be decrypted (we have developed an adapter module for doing this, so no problem with that)
Step 3 - It has to be FCC'ed (since it is a flat file) before sending it to the Integration Engine.
To execute these 3 steps sequentially, I have configured the Sender File Channel in the following way
Setting 1 - I have configured the necessary FCC parameters
Setting 2 - In the 'AdapterModules' tab, I have placed my custom developed decrypter adapter module first followed by the default 'CallSapAdapter' adapter module.
My question is, will the above setting suffice for carrying out my steps 1 - 3 in the correct order.
Basically I need to make sure that FCC is done only after decrypting the file.
So I need to confirm if FCC is being taken care by the 'CallSapAdapter' module.
Can anybody help me here plese?

Hi,
File adapter will check the FCC function first.So you will get error that time.Because you have encrypted data.So use the "MessageTransformBean"module for FCC.
Step 1 - An encrypted file has to be picked by the sender file channel
Step 2 - It has to be decrypted (we have developed an adapter module for doing this, so no problem with that)
Step 3-MessageTransformBean
Step 4-'CallSapAdapter' adapter module
Check the bellow link for "Message Transform Bean".
[http://help.sap.com/saphelp_nw70/helpdata/EN/57/0b2c4142aef623e10000000a155106/content.htm]
Regards,
Prakasu.M

What is the use of Module tab in Communication Channel ?

Hi Expertes
can any body tell me the that
What is the use of Module tab in Communication Channel ?
How we can use in the senarios?
Mainly What are the Situvation we can use this tab ?
Thank you
G,Praveen Kumar

hi rajesh
Thank You For Fast Responce
Error :
Exception caught by adapter framework: The following configuration errors were detected: - Either dataRec.fieldSeparator or dataRec.fieldLengths must be specified.
Delivery of the message to the application using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: The following configuration errors were detected: - Either dataRec.fieldSeparator or dataRec.fieldLengths must be specified : com.sap.aii.af.service.util.configuration.ConfigurationExceptionSet: The following configuration errors were detected: - Either dataRec.fieldSeparator or dataRec.fieldLengths must be specified.
Can you Help me torectifiy the error .

Hi all, Please suggest a case where there is a requirement for new SOAP sender adapter module. I wanted to develop a module but in my current project i am unable to find any such requirement.

Hi all, Please suggest a case where there is a requirement for new SOAP sender adapter module. I wanted to develop a module but in my current project i am unable to find any such requirement. So please give me inputs for the same..
Thank you,
Vinay Kumar A

You can try converting a synchrnous soap call to asynchronous using a custom module
Here your module will send a response back to the sender system and make an asynchronous call forward

HT5372 Someone tried to steal my phone, and there are 3 Japanese websites stored under my iCloud tabs. What does that mean??

Someone tried to steal my phone, and there are 3 Japanese websites stored under my iCloud tabs. What does that mean??

That they actually got ahold of the device and used the browser. Am I right?

Adapter Module Error-Sending excel file as an attachment of the mail

Hi ,
My scenario is as follows
1)I am sending an excel file as an attachment of the mail.I need to read that excel attachment as a payload.
So mail adapter is used in sender side.
To configure this, have used standard PayloadSwapBean module with proper module key.
Next to convert excel to XML another custom adapter module is being used.
Both this adapter module , I configured into the CC of sender mail adapter.
The order in which adapter modules are being used in the sender CC are as follows
1)localejbs/AF_Modules/PayloadSwapBean
2)localejbs/MDPExcelToXMLConversion
3)sap.com/com.sap.aii.adapter.mail.app/XIMailAdapterBean
MDPExcelToXMLConversion-Custom adapter module written to convert excel to xml.
I am getting the following error
exception caught during processing mail message [4899]com.sap.aii.af.lib.mp.module.ModuleException
And also,
no messages in coming MONI of PI.
Pls suggest what to do.
Thanks
Ayan

Shabarish,
Will the ordering in which the adapter modules(In this case there are two-PayloadSwapBean & MDPExcelToXML) are appearing into Module tab of sender adapter matter?
Firstly, what is happenning
1)If I take out the custom adapter module MDPExcelToXML and put only PayloadSwapBean then it is successfully converting mail attachment into the main Payload i.e PayloadSwapBean module is working.
2)Nextly, my local code( i.e java code without including standard Module specific method like ejbActivate(),ejbPassivate(),process() etc etc.)) for MDPExcelToXML is successfuly converting the excel file into the XML file.Then I am making the local code into adapter module specific code and deploying that.
A few question arises here,
Do I need to do any specific configurations here in PI for this particular things.Maybe both the adapter module is clashing with each other.
And also using tracing and logging into my custom adapter module code.Getting the following error,
java.io.IOException: Unable to read entire header; 116 bytes read; expected 512 bytes#
Thanks
Ayan

Adapter Modules

Hello,
While working with the Modules, I got the enterpise bean to work in a standalone fashion. But when I deployed the bean and configured the communication channel module tab, placing the bean first in the processing sequence, it doesnt seem to have any effect. I even tried writing messages from the Bean to the Audit log, but couldnt see it up there. Any clue folks?
Regards,
Ke N

When the bean works 'standalone', it might be sth. wrong with correct deployment.
What is the Adapter Monitoring in the Runtime Workbench telling you about the adapter with the included module?
Have you tried to restart the J2EE engine and test again?
Hope this helps
Dirk

In Adapter, MODULE tab, there is CallSAPAdapter : What is that?

Similar Messages

Maybe you are looking for