MTP Required on G.729 for RFC 2833?

I have a call that passes through the following devices:
Cisco 7942 --(SCCP)--> Cisco CME (28xx ISR) --(SIP Trunk)--> UCM 7.0 --(MGCP)--> Cisco 28xx ISR --> PRI
I'm not able to get DTMF to relay reliably when using G.729 (Annex A or B). In the Cisco UCM trace, I see "No more MTP resources available." I'm not sure why an MTP resource would be required for DTMF since it should be using RFC 2833 throughout.
The dial-peer on CME is:
dial-peer voice 2 voip
destination-pattern ....T
session protocol sipv2
session target ipv4:10.0.20.60
dtmf-relay rtp-nte
The MGCP configuration on the PRI gateway is:
mgcp
mgcp call-agent 10.0.20.60 2427 service-type mgcp version 0.1
mgcp dtmf-relay voip codec all mode nte-ca
mgcp rtp unreachable timeout 1000 action notify
mgcp modem passthrough voip mode nse
mgcp package-capability rtp-package
no mgcp package-capability res-package
mgcp package-capability sst-package
no mgcp package-capability fxr-package
mgcp package-capability pre-package
no mgcp timer receive-rtcp
mgcp sdp simple
mgcp rtp payload-type g726r16 static
I've tried both NTE modes on the gateway, neither seem to work. Any assistance would be greatly appreciated.

CM will need to invoke an MTP, unless you configure the MGCP gateway for RTP-NTE with:
mgcp dtmf-relay voip codec all mode nte-gw
If you configure that and flap the MGCP process and click 'reset gateway' from CM, CM will have that endpoint registered with an RTP-NTE cap, so since it is RTP-NTE on both sides, RTP-NTE will flow from CME directly to the MGCP gateway. If this still doesn't work, collect CM traces and these debugs for a failure, maybe there's a payload type issue.
MGCP gateway:
debug mgcp pack
debug voip rtp sess name
SIP gateway:
debug ccsip all
debug voip rtp sess name
The other option is to configure MGCP NTFY:
mgcp dtmf-relay voip codec all mode out-of-band
With this configuration, you need to have the MRG on the SIP trunk containing an IOS SW MTP for g.729 so that it can get invoked and terminate RTP-NTE and notify CM via SCCP that it needs to send an MGCP NTFY to the MGCP gateway.
For both configurations, make sure you configure 'rtp-nte' on the SIP trunk configuration in CM.

Similar Messages

Authorization Required for RFC user in R/3-APO system.

Could you please help regarding one authorization issue. I want to know the authorization required for one RFC user. Now this RFC user used for RFC connection of SAP R/3 - SAP APO system. user type is given dialog type and SAP_ALL profile has been given to this user id. Now I have to remove SAP_ALL from this user id in R/3 and APO system and provide the required the authorization in R/3 and APO system.
Regard
Auroshikha

The RFC authorisation depends completely on what the user is doing (ALEREMOTE?). We can't tell you what RFC auths your connection requires.
There is a guide to doing this here: https://wiki.sdn.sap.com/wiki/display/Security/BestPractice-HowtoanalyzeandsecureRFC+connections

** Sender Agreement is required for RFC but not IDoc, XI, & HTTP.. Why ?

Hi Friends,
All we know that since IDoc, XI adapters running on Integration Engine (SAP WAS 6.40), Sender Agreement is need not required.
Since RFC is proprietary document for SAP like IDoc, why we are creating Sender Agreement for RFC adpater ? (We know that RFC adpater is running on Adapter Engine, so that ...). Some of our guys asking me this question.
Why is this difference (IDoc adapter running on Integration Engine & RFC adapter is running on Adapter Engine) ? Anyboday can clarify the exact reason on this ...
Kind regards,
Jegathees P.

Hi,
RFC Adapter:
RFC adapter can abe to manage metadata while using the Jco call.This turns the RFC data to RFC xml message.
IDOC Adapter:
But Loading the metadata for IDOC we should create a port and rfc destination.IDOC adapter and metadata container placed in integration server before and after the pipeline step.metadata container converts the IDOC to IDOCxml.IDOC adapter converts the IDOC xml to native xml format.Using idx2 we uploaded the IDOC metadata with the help of RFC destination and port.
Regards,
Prakasu.M

Any SAP Note for RFC Error between BI and ECC 5.0

Hi..
the RFC Destination between BI and ECC 5.0 is giving errors.
Plz let me know if there is any Support pack or any solution to fix this error.
thanks..

Hi,
pls find the RFC connection details
1 Prerequisites
1.1 User Roles
Use
With the Building Block Connectivity a configuration role for each component is provided to access all transactions relevant for the installation. The following roles are available:
Technical name Description File name for upload
B02_01C B02 - Connectivity Configuration Role (SAP R/3) B02_01C.SAP
B02_03C B02 - Connectivity Configuration Role (SAP BW) B02_03C.SAP
C71_04C B02 - Connectivity Configuration Role (SAP CRM) C71_04C.SAP
B02_04C_SRM B02 - Connectivity Configuration Role (SAP SRM) B02_04C_SRM.SAP
Procedure
Please upload the necessary roles and add them to your user, using transactions PFCG (Role Maintenance).
2 Local Settings
This chapter describes all local settings that are necessary for each component like SAP R/3, SAP SCM, SAP BW, SAP CRM or SAP SRM.
2.1 SAP R/3
2.1.1 Define Client Administration (SAP R/3)
Use
This activity allows you to change Customizing settings.
Prerequisites
You have logged on to the system in English in order to start with the installation of the Best Practices Scenario.
Procedure
Run the following activity:
SAP R/3 Role Menu Define Client Administration (SAP R/3)
Transaction Code SCC4
SAP R/3 Menu Tools  Administration  Administration  Client Administration  Client Maintenance
Then carry out the following steps:
1. Choose Display  Change.
2. Confirm the warning message Caution: The table is cross client.
3. Select your SAP R/3 client and choose Details.
4. In the Change View Clients: Details screen, activate the following settings:
u2022 Automatic recording of changes
u2022 Changes to Repository and cross-client Customizing allowed
u2022 eCATT and CATT allowed.
5. Save.
6. Go back to the SAP Easy Access menu.
2.1.2 Defining a Logical System for SAP R/3 (SAP R/3)
Use
The purpose of this activity is to create a logical system for your SAP R/3 System. To enable communication between systems within your system landscape, you must
1. Define the systems as logical systems.
2. Assign the logical system for the SAP R/3 System to a client.
This enables the systems to recognize the target system as an RFC destination. If the logical system has already been created, skip this activity.
Logical systems are defined cross-client.
Procedure
Carry out the following steps:
1. Access the transaction using:
SAP R/3 Role Menu Defining a Logical System for SAP R/3 (SAP R/3)
Transaction Code SPRO
SAP R/3
IMG Menu Basis Components (for R/3 Enterprisse: SAP Web Application Server)  Application Link Enabling (ALE)  Sending and Receiving Systems  Logical systems  Define Logical System
2. Choose New entries.
3. In the column Log System, enter a name for the logical system that you want to create.
4. In the column Name, enter a description of the logical system.
Log. System Name
where XXX is the system name
and NNN is the client.
5. Save your entries.
A transport request for Workbench appears.
6. Select an existing request or create a new request, if necessary.
A transport request for Customizing appears.
7. Select an existing request or create a new request, if necessary.
2.1.3 Assigning Logical System to Client
Use
The purpose of this activity is to make an assignment for the logical system. Skip this activity if a logical system is already assigned to your client.
Procedure
Carry out the following steps:
1. Access the transaction using:
SAP R/3 Role Menu Assign Logical System to Client
Transaction Code SCC4
SAP R/3 Menu Tools  Administration  Administration  Client Administration  Client Maintenance
2. Choose Display ® Change.
3. Confirm the warning message The table is cross client.
4. Select your R/3 client and choose Details.
5. Enter the name of the logical system of your SAP R/3 client.
6. Save and confirm the warning message Be careful when changing the logical system.
7. Choose Back twice.
2.1.4 Creating an RFC User (SAP R/3)
Use
To enable communication between the SAP R/3 back-end system and the SAP SCM System, you have to create an RFC user in the SAP R/3 System.
The RFC user in the application client enables multiple RFC connections. Skip this activity if an RFC User has already been created.
Procedure
Carry out the following steps:
1. Access the transaction using:
SAP R/3 Role Menu Creating an RFC User (SAP R/3)
Transaction Code SU01
SAP R/3 Menu Tools  Administration  User Maintenance  Users
2. In the User field, enter RFCUSER.
3. Choose Create.
4. On the Maintain User screen, enter the following data on the Tab entry screens:
Address
Last Name
Function
Logon data
User type System
Password LOGIN
Profile
Profiles SAP_ALL
SAP_NEW
S_BI-WX_RFC
Defaults
Logon Language EN
5. Save your entries.
2.3 SAP BW
2.3.1 Define Client Administration
Use
This activity defines changes and transports of the client-dependent and client-independent objects.
Procedure
1. To perform this activity, choose one of the following navigation options:
SAP BW Role Menu Local Settings ® Define Client Administration
Transaction Code SCC4
SAP BW Menu Tools  Administration  Administration  Client Administration  Client Maintenance
2. Switch to change mode.
3. Select your client.
4. Choose details.
5. In field Currency enter the ISO-code of the local currency, e.g. USD or EUR.
6. In field Client Role enter Customizing
7. Check the settings for changes and transport of client-specific objects and client-independent object changes
If you want to use the settings made by BC-Sets or manually in other systems (other than BW), u201CAutomatic recording of changesu201D and u201CChanges to Repository object and cross-client Customizing allowedu201D is required.
Result
Client administration has been defined to support the installation using Best Practices.
2.3.2 Defining a Logical System for SAP BW (SAP BW)
Use
In this step, you define the logical systems in your distributed system.
Prerequisites
Logical systems are defined cross-client. Therefore cross-client customizing must be allowed in your client (this can be checked in transaction SCC4).
Procedure
To carry out the activity, choose one of the following navigation options:
SAP BW Role Menu Defining a Logical System for SAP BW (SAP BW)
Transaction Code SPRO
IMG Menu SAP Reference IMG  SAP Customizing Implementation Guide  SAP NetWeaver  Business Information Warehouse  Links to other Systems  General Connection Settings  Define Logical System
1. A dialog box informs you that the table is cross-client. Choose Continue.
2. On the Change View u201CLogical Systemsu201D: Overview screen, choose New entries.
3. On the New Entries: Overview of Added Entries screen enter the following data:
Field name Description R/O/C User action and values Note
Log. System Technical Name of the Logical System Enter a name for the logical BW system that you want to create
Name Textual Description of the Logical System Enter a clear description for the logical BW system
4. Choose Save.
If a transport request for workbench and customizing is displayed choose existing requests or create new requests.
If you want to continue with the next activity, do not leave the transaction.
Result
You have created a Logical System Name for your SAP BW client.
2.3.3 Assigning Logical System to Client (SAP BW)
Procedure
To carry out the activity, choose one of the following navigation options:
SAP BW
Role Menu Assigning Logical System to Client (SAP BW)
Transaction Code SCC4
SAP BW Menu Tools  Administration  Administration  Client Administration  Client Maintenance
1. In the view Display View "Clients": Overview, choose Display.  Change
2. Confirm the message.
3. Select your BW client.
4. Choose Details.
5. In the view Change View "Clients": Details, insert your BW system in the Logical system field, for example, BS7CLNT100.
6. Save the entries and go back.
2.3.4 Opening Administrator Workbench
Procedure
To carry out the activity, choose one of the following navigation options
SAP BW Modeling  Administrator Workbench: Modeling
Transaction Code RSA1
1. In the Replicate Metadata dialog box, choose Only Activate.
2. If a message appears that you are only authorized to work in client ... (Brain 009) refer to SAP Note 316923 (do not import the support package, but use the description under section Workaround).
2.3.5 Creating an RFC-User (SAP BW)
Procedure
To carry out the activity, choose one of the following navigation options:
SAP BW Role Menu Creating RFC User
Transaction Code SU01
SAP BW Menu Tools  Administration  User Maintenance  Users
Then carry out the following steps:
1. On the User Maintenance: Initial Screen screen:
a. Enter the following data:
Field Entry
User RFCUSER
b. Choose Create.
2. On the Maintain User screen:
a. Choose the Address tab.
b. Enter the following data:
Field Entry
Last Name RFCUSER
Function Default-User for RFC connection
c. Choose the Logon data tab.
d. Enter the following data:
Field Entry
Password LOGIN
User type System
e. Choose the Profiles tab.
f. Enter the following data:
Field Entry
Profiles SAP_ALL , SAP_NEW and S_BI-WHM_RFC
g. Choose Save.
Do not change the password of this user as it is used in RFC connections.
2.3.6 Define RFC-USER as default (SAP BW)
Procedure
To carry out the activity, choose one of the following navigation options
SAP BW Role Menu Define RFC-USER as default (SAP BW)
Transaction Code RSA1
SAP BW Menu Modeling  Administrator Workbench: Modeling
1. On the Administrator Workbench: Modeling screen choose Settings  Global Settings.
2. In the Global Settings/Customizing dialog box choose Glob. Settings.
3. On the Display View u201CRSADMINA Maintenance Viewu201D: Details screen:
a. Choose Display  Change.
b. Enter RFCUSER in the BW User ALE field.
c. Choose Save.
Hope this helps in solving u r problem
Regards
Ramakrishna Kamurthy

Password for RFC USer

Hi experts,
We need to set the password for RFC User in small letters.But we are not able to do it ,because of our 'login/*' parameter values.
Is there is any other method to create the password for User ID with small letters(Ex:welcome,hello)?
Thanks in Advance,
Karthika

> > Login rules are not specific to user types. It is same for all type of users.
> Sorry, this is not correct. The password validity rules are a good example which don't apply to SYSTEM and SERVICE type users. Other examples are the idle time rules and compliance to policy rules and the logon ticket rules and remote login via debugging rules and...
>
I tried to talk about is as per the ongoing discussion topic i.e. Case sensitiveness of Passwords and not other attributes. So from this point of view there is no such separate rule applies during admin imposed password or during a change (the cases where system prompts for changing password).
> > From NAS 7 there is a change in the password rules.
> There were major changes in 46B, and 6.10 and 6.40 as well, and Karthika still has not told us which release she is on.
>
Agreed totally.
> > [Note 750390 - USR02: various problems with password attributes|https://service.sap.com/sap/support/notes/750390]
> > [Note 624635 - Error messages with password change using RFC function|https://service.sap.com/sap/support/notes/624635]
> I cannot see how these notes are related to this silly requirement of setting a lower-case only password.
>
I didn't went through in details fully but seen it contains a considerable error details.... may be of any help to OP.
> I think either Karthika is playing a joke on us, or the person interviewing Karthika is playing a joke on her... These would be the only logical explanations left which I can see for for such a requirement.
>
May be.. but of course need more information and purpose of such strictness for setting such password. Also the FM PASSWORD_FORMAL_CHECK can be used with required customizations but you are the best person to tell this properly.
regards,
Dipanjan

Required Help and Documentations for following Scenarios. URGENT

Hi every one,
I require help and materials for following scenarios:
<b>1) RFC to IDOC
2) JDBC to RFC & IDOC
3) Mail to File
4) HTTP to RFC, JDBC & IDOC
5)WEB SERVICES to RFC & IDOC
6) IDOC to ABAP proxy
7) Java Proxy to JDBC</b>
my email id: <u>[email protected]</u>
urgent plzz help me...
Message was edited by:
satish c

Satish,
I would suggest to go through sravyas weblogs where she has given all the links to all the scenarios:
/people/sravya.talanki2/blog/2006/12/25/aspirant-to-learn-sap-xiyou-won-the-jackpot-if-you-read-this-part-i
/people/sravya.talanki2/blog/2006/12/26/aspirant-to-learn-sap-xiyou-won-the-jackpot-if-you-read-this-part-ii
/people/sravya.talanki2/blog/2006/12/27/aspirant-to-learn-sap-xiyou-won-the-jackpot-if-you-read-this-part-iii
Also check this weblogs which they have explained with some scenarios:
Following are the links to weblogs which will help to develop the basic scenarios.
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters - IDoc to File
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy - ABAP Proxy to File
/people/sap.user72/blog/2005/06/01/file-to-jdbc-adapter-using-sap-xi-30 - File to JDBC
/people/prateek.shah/blog/2005/06/14/file-to-r3-via-abap-proxy - File to ABAP Proxy
/people/venkat.donela/blog/2005/03/02/introduction-to-simplefile-xi-filescenario-and-complete-walk-through-for-starterspart1 - File to File Part 1
/people/venkat.donela/blog/2005/03/03/introduction-to-simple-file-xi-filescenario-and-complete-walk-through-for-starterspart2 - File to File Part 2
/people/ravikumar.allampallam/blog/2005/06/24/convert-any-flat-file-to-any-idoc-java-mapping - Any flat file to any Idoc
/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit - File to RFC
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1685 [original link is broken] [original link is broken] [original link is broken] [original link is broken] - File to Mail
/people/jayakrishnan.nair/blog/2005/06/20/dynamic-file-name-using-xi-30-sp12-part--i - Dynamic File Name Part 1
/people/jayakrishnan.nair/blog/2005/06/28/dynamic-file-namexslt-mapping-with-java-enhancement-using-xi-30-sp12-part-ii - Dynamic File Name Part 2
/people/michal.krawczyk2/blog/2005/03/07/mail-adapter-xi--how-to-implement-dynamic-mail-address - Dynamic Mail Address
/people/siva.maranani/blog/2005/05/25/understanding-message-flow-in-xi - Message Flow in XI
/people/krishna.moorthyp/blog/2005/06/09/walkthrough-with-bpm - Walk through BPM
/people/siva.maranani/blog/2005/05/22/schedule-your-bpm - Schedule BPM
/people/sriram.vasudevan3/blog/2005/01/11/demonstrating-use-of-synchronous-asynchronous-bridge-to-integrate-synchronous-and-asynchronous-systems-using-ccbpm-in-sap-xi - Use of Synch - Asynch bridge in ccBPM
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1403 [original link is broken] [original link is broken] [original link is broken] [original link is broken] - Use of Synch - Asynch bridge in ccBPM
/people/michal.krawczyk2/blog/2005/08/22/xi-maintain-rfc-destinations-centrally - Maintain RFC destination centrally
/people/sravya.talanki2/blog/2005/08/18/triggering-e-mails-to-shared-folders-of-sap-is-u - Triggering Email from folder
/people/sravya.talanki2/blog/2005/08/17/outbound-idocs--work-around-using-party - Handling different partners for IDoc
/people/siva.maranani/blog/2005/08/27/modeling-integration-scenario146s-in-xi - Modeling Integration Scenario in XI
/people/michal.krawczyk2/blog/2005/08/25/xi-sending-a-message-without-the-use-of-an-adapter-not-possible - Testing of integration process
/people/michal.krawczyk2/blog/2005/05/25/xi-how-to-add-authorizations-to-repository-objects - Authorization in XI
http://help.sap.com/saphelp_nw04/helpdata/en/58/d22940cbf2195de10000000a1550b0/content.htm - Authorization in XI
/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--step-by-step - Alert Configuration
/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--troubleshooting-guide - Trouble shoot alert config
/people/sameer.shadab/blog/2005/09/21/executing-unix-shell-script-using-operating-system-command-in-xi - Call UNIX Shell Script
/people/sravya.talanki2/blog/2005/11/02/overview-of-transition-from-dev-to-qa-in-xi - Transport in XI
/people/r.eijpe/blog/2005/11/04/using-abap-xslt-extensions-for-xi-mapping - Using ABAP XSLT Extensions for XI Mapping
/people/prasad.ulagappan2/blog/2005/06/07/mail-adapter-scenarios-150-sap-exchange-infrastructure - Mail Adaptor options
/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm - Collection of IDoc to Single File
/people/sap.user72/blog/2005/11/17/xi-controlling-access-to-sensitive-interfaces - Controlling access to Sensitive Interfaces
/people/michal.krawczyk2/blog/2005/11/10/xi-the-same-filename-from-a-sender-to-a-receiver-file-adapter--sp14 - The same filename from a sender to a receiver file adapter - SP14
/people/prasad.illapani/blog/2005/11/14/payload-based-message-search-in-xi30-using-trex-engine - Payload Based Message Search in XI30 using Trex Engine /people/sap.user72/blog/2005/11/24/xi-configuring-ccms-monitoring-for-xi-part-i - XI : Configuring CCMS Monitoring for XI- Part I
/people/michal.krawczyk2/blog/2005/11/23/xi-html-e-mails-from-the-receiver-mail-adapter - XI: HTML e-mails from the receiver mail adapter
/people/sap.user72/blog/2005/11/22/xi-faqs-provided-by-sap-updated - XI : FAQ's Provided by SAP
Regards,
---Satish

'Classic' RFC library - password limited for rfc calls ?

Hi ,
we are using the 'classic' RFC library to connect to SAP for calling RFC function modules. Due to the fact that there are often older SAP systems involed, we use only passwords with 8 digits. But now we have the requirement to use passwords for the rfc user with more than 8 digits. According to my todays knowlede, the password is limited to 8 digits with the standard rfc lib.
Can the newer SAP NW RFC lib handle a password with more than 8 digits ?
But am i right that the SAPNW RFC lib is unable to handle rfc calls with opening a SAPGUI ?
thx
Heike

Hi,
thank you for your answer!
I have investigated something new yesterday:
I thought at the beginning, that the problem just occurs, when the system work processes are reached. The system has for example set up 15 dialog processes and the external server is calling the function 20 times in parallel. Then we normally need 5 dialog processes more. The system is taking then all 15 dialog processes and the locks got stucked.
That means, that I´ll maybe only get 4 or 5 uploads, which have really been updated the tables. All the others couldn´t get the table locked for their process.
But if I now let the server call the function just about 13 times in parallel, nearly all uploads have been updated the table!
From my point of view, the lock from SAP gets stucked, when the limit of dialog processes is reached. It´s not working in the right way anymore...
The same is happening, when you set up in the system, that only 10 work proecesses can be used by RFC. If I have more than 10, it´s going to be critical with the locks....
WEIRD!
Can anybody help me out of trouble?
Thank you!

PI 7.11 - Alert creation for RFC Exceptions does not work

Hi folks!
In our PI 7.11 SP04 system we have created an Alert Category as well as an Alert Rule to be informed about errorneous messages in the Integration Engine (ABAP).
The scenario is synchronous SOAP Axis to sRFC, where the RFC answers with an exception that is transferred to a SOAP Fault response message.
Now we see messages with Application Errors in the Integration Engine, but no alert is created. Having a look at the alert creation log using report SXMSALERT_LOGREADER shows us that the system even does not try to create an alert for these messages. Alerts are only created for errors in the Adapter Engine.
Question:
Why does the system not create alerts in this case and how can we achieve this?
Thanx for any hint!
Kind Regards,
Volker

Hi!
Additional information for all:
When forcing an error like "receiver not found" both kinds of alerts are created: AE Alert and IE Alert. Thus in general the alert configuration and the alert rule for IE errors are correct and working - only not for RFC exceptions ....
Regards,
Volker

Is autoconfig required to be run for apps password change

Is autoconfig required to be run for apps password change -- We are only changing APPS and APPLSYS passwords.
How to Change Applications Passwords using Applications Schema Password Change Utility (FNDCPASS or AFPASSWD) [ID 437260.1] -- does not mention anything about autoconfig.
Please clarify.
Thanks

It's mentioned in the document twice
1. For APPLSYSPUB/GUEST as you mentioned
2. Under "Verify the new password" which cover the apps/applsys passwords
If you search the doc for "AutoConfig" you will find it there.
Thanks,
Hussein

RFC destination for RFC to File scenario

Hi,
I m creating a TCP/IP RFC destination in R/3 system for my RFC to File scenario.
Step 1:
For this a Registered server program is created in Jco RFc Destinations with,
Program Id : pgm1
Gateway host : PI's host
Gateway service : PI's service
application server host: ECC's host
system numer     : ECC's number
client : ECC's client
logon user : ECC user
password : pwd
Step 2:
In SM59, TCP/IP connection the following parameters are given:
Program ID : pgm1
Gateway host : PI's host       -
> is this correct
Gateway service : PI's service      -
> is this correct
Step 3:
So i am calling the RFC in ABAP program (R/3 system) like:
CALL FUNCTION 'Z_HR_OUTBOUND_DATA2'
IN BACKGROUND TASK DESTINATION 'Z_HR_OUTBOUND_DATA2'
Step 4:
In PI side,
for RFC sender I am passing :
Application server : PI server
Application server service: PI host
program ID: pgm1 which was created in the previos step
For RFC Metadata Repository Parameter, i am passing all the values related to R/3
Please let me know whether the steps and values i given is correct.
B'cos even if i give ECC's information in Gateway host and Gateway service the scenario works fine and if i PI's info then also it works fine.
so i am confused as which is the correct method. pls clarify

Ok I will try to explain....
Assumptions: R3_TO_XI is the name of RFC which I created in ECC of type T.
While creating the RFC in ECC we mention a unique name which is called Progaram ID. Now the same program id we mention in our sender RFC CC.
So now when an ABAP Progarm (where you will call this RFC with it's destination) is scheduled/triggered with the code as mentioned below then since the DESTINATION ('R3_TO_XI') mentioned here contain the same program id which we have mentioned in our sender CC, invokes the adapter in PI and soon after that all pipeline steps get executed in XI.
CALL FUNCTION 'ZBAPI_COMPANY_GETDETAIL'
IN BACKGROUND TASK
DESTINATION 'R3_TO_XI'
TABLES
    comp_detail = company_detail.
COMMIT WORK.
Regards,
Sarvesh

Getting metadata for RFCs using RFC SDK (with position of parameters)

Hi!
I'm currently using the RFC SDK Function "RfcGetFunctionInfoAsTable" to retrieve metadata for RFCs from SAP. What i see is that the "Position" field in the RFC_FIELDS_U structure contains arbitrary values, and so I am not able to determine what is the actual ordering of the parameters.
What can I do to determine the exact ordering of the parameters of an RFC? (ordering as in - I want to obtain the parameters in the same order as they appear in SAP GUI).
Thanks,
Mustansir

Hi,
I think you can use the code similar to the one below...
some of the things not covered in this are
1. all types for which   CALL FUNCTION 'RFC_GET_NAMETAB' is not returning result, you can call CALL FUNCTION 'RFC_GET_STRUCTURE_DEFINITION' directly. I have not covered that in this code. Hope this is helps in resolving your issue.
Also, the code is not optimized. So there is some scope for optimization of this code.
REPORT ZTEST_GET_SREUCTURE.
DATA : PARAMS     type table of     RFC_FUNINT,
      ls_params like line of params.
data: NAMETAB     type table of     X031L,
      ls_NAMETAB like line of NAMETAB.
data: FIELDS type table of RFC_FIELDS,
      ls_fields like line of fields.
CALL FUNCTION 'RFC_GET_FUNCTION_INTERFACE'
EXPORTING
    FUNCNAME                      = 'fm_test_fm'
TABLES
    PARAMS                        = PARAMS
IF SY-SUBRC <> 0.
ENDIF.
loop at params into ls_params.
CALL FUNCTION 'RFC_GET_NAMETAB'
    EXPORTING
      TABNAME                     = LS_PARAMS-TABNAME
    TABLES
      NAMETAB                     = NAMETAB
IF SY-SUBRC <> 0.
ENDIF.
loop at NAMETAB into ls_NAMETAB.
    CALL FUNCTION 'RFC_GET_STRUCTURE_DEFINITION'
EXPORTING
    TABNAME                     = LS_NAMETAB-ROLLNAME
TABLES
    FIELDS                      = FIELDS
    loop at fields into ls_fields.
      write: ls_fields-FIELDNAME.
    endloop.
endloop.
endloop.

XML pay load for RFC call in java mapping

Hi,
I searched in many forums about the payload to be given for RFC Lookup from a functional module,but i think i am not able to get it correct.
Can any one please give me the exact structure of XML Payload to be sent while invoking the function module via RFC LOOKUP
Say i have 2 import parameters(input1,input2) and one output(output1)......
Thanks in advance,
H.L.Babu

>
hlbabu123 wrote:
> Hi,
> I searched in many forums about the payload to be given for RFC Lookup from a functional module,but i think i am not able to get it correct.
>
> Can any one please give me the exact structure of XML Payload to be sent while invoking the function module via RFC LOOKUP
>
> Say i have 2 import parameters(input1,input2) and one output(output1)......
>
> Thanks in advance,
> H.L.Babu
have a look at this document - https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/a03e7b02-eea4-2910-089f-8214c6d1b439&overridelayout=true
in case u still have issues do get back

Require a Message mapping for this Logic.

Hi Experts,
I require a Message mapping for this Logic.
In the Source there are 4 fields and, the Target side, the fields should appear like this.
Source Structure- File
Record
|-> Header
Order_No
Date
|-> Item
Mat_No
Quantity
Target Structure-IDoc
IDoc
|-> Header
|-> Segment
Delivery_Order_No
Recv_Date
|-> Item
|-> Segment
Delivery_Order_No
Material_Num
Recv_Quantity.
The Logic is for every Order number an IDOC is generated.And if the Material num matches then the quantity should be added. and important note is that the material numbers are different for every order number. That means if a material number is 2 in the order number A. Then the material number can never be 2 in any of the order numbers.Here is the following with an example for the above scenario.
For example:-
we have
Source Structure- File
Order-no Date Mat_No Quantity
1 01/02/2011 A 10
1 01/02/2011 B 15
1 01/02/2011 A 10
2 01/02/2011 C 10
2 01/02/2011 C 10
3 01/02/2011 D 20
3 01/02/2011 D 10
3 01/02/2011 E 25
Target Structure-IDoc
Delivery_Order_No Recv_Date Material_Num Recv_Quantity
1 01/02/2011 A 20
1 01/02/2011 B 15
2 01/02/2011 C 20
3 01/02/2011 D 30
3 01/02/2011 E 25
So for this example total of 5-Idocs created. That means for this example if Order_No is 1 When the Mat_No is A the quantity gets added. For this Scenario 1 IDoc with four Fields 2 in Header(Delivery_Order_No, Recv_Date) and 2 in Item(Material_Num, Recv_Quantity) is generated by adding the quantity field in the Target Side. Similarly if Order_No is 1 when the Mat_No is B then separate IDoc is generated with four Fields 2 in Header(Delivery_Order_No, Recv_Date) and 2 in Item(Material_Num, Recv_Quantity) in the Target Side. Similarly, if Order_No is 2 when the Mat_No is C, an IDoc is generated with four Fields 2 in Header(Delivery_Order_No, Recv_Date) and 2 in Item(Material_Num, Recv_Quantity) by adding the quantity field in the Target Side. ike wise the process goes on upto 3.Kindly do the needy..
Thanq very much in advance..
Edited by: Prashanth Bharadwaj on Oct 17, 2011 1:29 PM

Hi Prashanth,
Concatinate the two fields OrderNo and MaterialNo and follow the below logic which will resolve your problem.
concatinationOfOrderNo&MaterialNo>removecontext>sort>splitByValueChange>collapseContext-->IDOC
concatinationOfOrderNo&MaterialNo>removecontext>sort>splitByValueChange>collapseContext>splitByEachValue>subString(0,1)-->Delivery_Order_No
formatByExample>collapseContext>SplitByEachValue-->Recv_Date
FormatByExample:
input1:resulrOfSortByKey
input2:concatination>removecontext>sort-->SplitByValuChange
sortByKey:
input1:concatination-->removecontext
input2:date-->removecontext
concatinationOfOrderNo&MaterialNo>removecontext>sort>splitByValueChange>collapseContext>splitByEachValue>subString(1,1)-->Material_Num
formatByExample>sum>Recv_Quantity
FormatByExample:
input1:sortByKey
input2:concatination>removecontext>sort-->SplitByValueChange
SortByKey:
input1:concatination-->removecontext
input2:Quantity-->removeContext
Regards,
Priyanka.

Does IC WebClient require a J2EE engine for any of its component

Does IC WebClient requires a J2EE engine for any of its component? What's the need to install j2ee engine on CRM server?
I would appreciate if anybody could give a good answer or any kind of documentation on it.

Prakash,
The answer is yes in terms of the J2EE enginge being required. It primarily handles your multichannel access and broadcast messaging for the call center. If you don't install it, then your IC webclient will not work correctly. We are not using the "telphony" features of the call center, but still installed the java piece so that the standard functionality would work correctly.
Good luck,
Stephen

Runtime Error: "Time out" for RFC.

Hi,
During RFC, I am getting a runtime error stating "Timeout error". Even while the job is run in background I am getting this error. Seems like the time for RFC task is set to 600 secs.
How to resolve this and is there any way we can see time limit set for different tasks?
thanks,
Arun

Hi,
   More info: I am using multithreading or mass processing technique, so the logic has to be written in FM which has RFC enabled. So while the task is in process in background it exceeds the time limit set for RFC i.e 600secs.
Sample code:
    CALL FUNCTION 'ZZ_ABC'
      STARTING NEW TASK gv_task
      DESTINATION IN GROUP gv_grp
      PERFORMING rcvb_endprocess ON END OF TASK
      EXPORTING
        e_batch_date = gv_batch_date
FORM rcvb_endprocess                                        "#EC CALLED
              USING gv_task TYPE any.                      "#EC NEEDED
RECEIVE RESULTS FROM FUNCTION 'ZZ_ABC'
   TABLES
        t_receivables = it_receivables.
gv_rcvd = gv_rcvd + 1.
ENDFORM.                    " RCVB_ENDPROCESS

MTP Required on G.729 for RFC 2833?

Similar Messages

Maybe you are looking for