XI TO BI - RFC Issue

Hi,
In XI to BI integration, am importing an RFC from BI to XI. After importing I noticed in one of the field name the character "/" are replaced with "_".
Following is the field name in RFC in BI " /BIC/ZTYPE_ADJ" after importing that in XI it becomes like this "_-BIC_-ZTYPE_ADJ". Even the RFC name changes
Original Name : /BIC/CQZGG_GR_00001000
After importing : -BIC-CQZGG_GR_00001000
The issue is actually with the field name which is not passing the value because of this conversion. BI is not recognizing the field name.
Any thoughts on this.
Thanks
Ashok

Ashok,
>Following is the field name in RFC in BI " /BIC/ZTYPE_ADJ" after importing that in XI it becomes like this "_-BIC_-ZTYPE_ADJ".
You need to connect thru Proxy code.
Cheers
Agasthuri

Similar Messages

  • SAP R/3 to External System RFC issue

    Hi Experts,
    We have one Peculiar issue in our SAP R/3. Request you to help me in resolving this.
    Order Processing:
    During Sales Orders Processing, for every line item a RFC is being initiated from SAP R/3 to an external system called Trilogy Pricer to get the Pricing data.  Trilogy Pricer sends the Pricing data to SAP R/3 and the respective Orders are being processed in SAP R/3.
    Current Issue:
    The issue we are facing is that, once the Pricing data is sent to SAP R/3, Trilogy Pricer expects an acknowledgement (RFC_OK) from SAP R/3 in order to release the RFC connection.  Intermittently, Trilogy Pricer is not receiving this or any kind of acknowledgement from SAP R/3 causing the connection to hang which is causing several problems.
    For example:
    On every business day, there will be 50,000 Sales orders.
    So, 5 or 10 sales orders are getting hanged every day.
    We tried to simulate this issue in Dev and Stage environments by processing 30,000 to 40,000 sales orders.
    But we were unsuccessful, which means all the RFC connections were being closed as the external system is able to get the acknowledgements for all those orders from SAP R/3.
    We are having this problem only in Prod.
    Any thoughts to solve this issue is highly appreciated.
    Advance thanks for your great help.
    Thanks and Regards,
    Srinivasa

    Hi I am not sure if it was similar issue, but I once had a kindaa problem I solved using
    CALL FUNCTION func STARTING NEW TASK task
                  [DESTINATION {dest}]
                  [{PERFORMING subr}|ON END OF TASK].

  • SAP R/3 to External System RFC issue during Sales Order Processing

    Hi Experts,
    We have one Peculiar issue in our SAP R/3. Request you to help me in resolving this.
    Order Processing:
    During Sales Orders Processing, for every line item a RFC is being initiated from SAP R/3 to an external system called Trilogy Pricer to get the Pricing data. 
    Trilogy Pricer sends the Pricing data to SAP R/3 and the respective Orders are being processed in SAP R/3.
    Current Issue:
    The issue we are facing is that, once the Pricing data is sent to SAP R/3, Trilogy Pricer expects an acknowledgement (RFC_OK) from SAP R/3 in order to release the RFC connection.  Intermittently, Trilogy Pricer is not receiving this or any kind of acknowledgement from SAP R/3 causing the connection to hang which is causing several problems.
    For example:
    On every business day, there will be 50,000 Sales orders.
    So, 5 or 10 sales orders are getting hanged every day.
    We tried to simulate this issue in Dev and Stage environments by processing 30,000 to 40,000 sales orders.
    But we were unsuccessful, which means all the RFC connections were being closed as the external system is able to get the acknowledgements for all those orders from SAP R/3.
    We are having this problem only in Prod.
    Any thoughts to solve this issue is highly appreciated.
    Advance thanks for your great help.
    Thanks and Regards,
    Srinivasa

    Hi I am not sure if it was similar issue, but I once had a kindaa problem I solved using
    CALL FUNCTION func STARTING NEW TASK task
                  [DESTINATION {dest}]
                  [{PERFORMING subr}|ON END OF TASK].

  • IDoc - XI - RFC Issues

    Trying to set up an IDoc->XI->RFC Scenario.  Am able to receive the IDoc into XI but are having issues getting this to the other system via RFC.
    Status in Monitor for Processed XML Messages (SXMB_MONI) is "Recorded for Outbound Processing".  When I "display" the specifics I see the Inbound Message was processed fine but the Receiver Grouping is set to "Recorded for Outbound Processing". 
    I check SMQ2 and I can see my data in the status "Transaction Recorded".  I try to <F6> the message in SMQ2 and get the message "the queue is registered and therefore cannot be activated".
    Also in SMQR the scheduler status is "Inactive".  Not sure if that is relevant or not.
    Hoping someone has seen this and can help me get whatever I'm missing set up!
    Thanks!

    Hi,
    <i>Also in SMQR the scheduler status is "Inactive". Not sure if that is relevant or not.</i>
    This status is OK.
    <i>I check SMQ2 and I can see my data in the status "Transaction Recorded". I try to <F6> the message in SMQ2 and get the message "the queue is registered and therefore cannot be activated".</i>
    >> in SMQ2 what is the status ? Is it running/sysfail etc ?
    If it is SYSFAIL, then double click on that and check the exact error.
    Else, you can go to SMQR or SXMB_ADM->Manage Queues->QRFC monitor->  .. then go to specified Queue name(whatever having the problem) and deregister it. Then go to SMQ2 and execute/activate the Queue . This time you will not get the info "Queue is registered...." Then go again SMQR and Re-reigister it.
    For more ~
    /people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
    Re: Recorded for Outbound Processing
    Hope this helps,
    Regards,
    Moorthy

  • RFC issue in Triggering workflow

    Hi,
    I am trying to trigger a custom workflow from EP in Newly set up ECC 6.0 system.
    Problem here is, Business object Event is getting triggered in R/3 with custom workflow as reciever, but the workflow is not going to the first stepThe event trace (SWEL) gives following information,
    Action                   Receiver started correctly
    RFC Status           Logon not possible (error in license check)
    I have checked the configuration in SWU3, all where fine, also the RFC WORKFLOW_LOCAL_100 tested successfully. The ECC6.0 has the full license.
    Please let me know why this has happened? How can it be solved? Please reply ASAP.
    Thanks,
    Shrinivas

    Hi,
    WF-BATCH has validity till 12/31/9999 and also the workflow initiator has SAP_ALL authorization,
    Still the issue has not been solved. New thing i noticed this this problem happens intermittently !
    For some time it is working fine, some other time its giving the same RFC error.
    Thanks,
    Shrinivas

  • File to RFC Issue

    Hi All,
    I am doing a File to RFC async scenario. I have done the related development in ESR and ID. While testing the file adapter picks the file does the required content conversion and is successful . When I check the RFC adapter it also shows successful. But the problem is the payload is the same as it was in the sender adapter. I mean after mapping the payload must change to the target message. Somehow in the RFC adapter I am seeing the same source payload. I deleted the Service interfaces, deleted the channels, deleted the ICO and recreated everything again but still the same issue. Can someone please provide inputs on the same. All configurations look correct. Ideally the message has not reached ECC but atleast the payload conversion should have happened.

    Hi Amit
    Check the log in message monitoring and see whether the operation mapping has been called or not.
    Also with the default configuration we can only see the payload before mapping in RWB.
    If you need to see the payload after the mapping then you need to add the below entries in NWA
    Goto configuartion-->infrastructure-->Java system properties--->services
    Choose the service XPI Adapter:XI and change the below property
    Then once you open the message in RWB, you see one more entry with AM which will show the payload generated after mapping.

  • File to RFC Issue in QA

    Hi Grus,
    I have developed File FCC to RFC in DEV and its good.
    After Moving this to QA, We tested but no data found in RFC System.
    Then I monitored and found that, File triggered from source directory and created a message with Outbound Interface and seen in Message Monitoring.
    But I did not see any message in RWB with ZFunction Module as Inbound Interface.
    What may be the issue?
    Regards,
    Durga.

    Hi Durga
    Have you found any error message in PI?
    May be the message has failed in mapping step, in that case you will not be able to see any message with ZFunction Module as Inbound Interface.
    Please check in PI and see if the message is failed or not?

  • Solution Manager RFC issues

    Hi Folks,
    We are facing problem with RFC connection from Quality to Solution Manager. It says " No authroization for trusted system" however the RFC connection from Solman to Quality is working fine.
    in SMSY -> RFC connection test working fine and able to fetch the qas to solman system. We have give all required authorization including SAP_ALL, SAP_NEW and S_RFC_XX Objects also assigned.
    It would be of great help if some one can help us on this.
    Regards,
    Vinod

    Hi
    Please check the "Troubleshooting in Trusted/trustng system" part in below link
    [http://help.sap.com/saphelp_nw04/helpdata/en/22/042671488911d189490000e829fbbd/content.htm|http://help.sap.com/saphelp_nw04/helpdata/en/22/042671488911d189490000e829fbbd/content.htm]
    Hope this help to fix the issue,
    Thanks,
    Jansi

  • CCMS: CEN configuration - Registration Failed due to RFC  : Issue Resolved.

    Hi There!
    I was trying for CEN-CCMS setup and I was bale to connect my other systems to the CEN, infact I was able to connect all the system, but somehow my DEV box is detached from the CEN box. When I try to run sapccmsr -R -j2ee pf= to register with CEN, at the end of  when I enter the details of "csmreg" user of CEN, throws the following error.
    INFO: Updated saprfc.ini in agent work directory /usr/sap/ccms/DEV_02/sapccmsr
    ERROR: Registration failed: Can't get version of DEV. RfcRc = 2, C_CALL_FAILED
    RFC Error Info for SALS_MS_GET_LOCAL_MS_INFO
    message:
    status:  EXCEPTION C_CALL_FAILED RAISED
    intstat:
    INFO: dsr: dsrlib unloaded.
    EXITING with code 1
    Illegal instruction (core dumped}
    In SM59, the TCP/IP rfc name with those program ID throws error. "Error when opening RFC connection". If I creadted the Program-ID in VA, then SM59 will pass the test connection, but its not the resolution, the DEV box is still detached from CEN.
    I redo the configuration with new CSMCONF too
    If I check the "monitored Remote System/RZ21 on CEN, it throws:
    > Connection test to destination DEV_CCMS_COLLECT terminated with ERRORS
    > Error when calling the underlying C function (function 'SALS_MS_GET_L..
    I followed the SAP's monitoring guide for NW04s-SP-13
    PI-7.0, SP-14
    Thanks anyways
    vipin
    Issue Resolved.
    Edited by: Vipin Sagar on Jul 22, 2008 4:08 AM

    Hi All,
    can any one share the solution for the above error.
    I am getting the same error for one of the systems. other systems are working fine.
    Thanks and regards,
    Sunny

  • RFC issue with TREX CCMS monitoring

    Hello,
    I have a TREX 7.10 instance (running on a Windows Server) and a SAP Solution Manager System 7.01 (on Unix Server) which is used as central CCMS monitoring system.
    I have configured CCMS Monitoring for TREX according to the pdf document that is attached to SAP note 897226 ('Monitoring TREX with CCMS. Alerting seems to work, the autoreaction method that I defined for e.g. unavailabitlity of TREX processes is triggered when I test it.
    In SolMan system, transaction RZ21, agents for remote systems,  I see that the agent for the TREX instance is in status 'Online'.
    But when I highlight this agent and click on the button 'Test Connection' I get  'Error when opening an RFC connection'.
    In TA SM59 of SolMan system I am doing connection check for the two TCP/IP RFC destination related with that TREX instance
    N3STAT.<hostname>.<Nr>   and
    SAPCCMSR.<hostname>.<Nr>
    For both I get the error 'program <hostname>.n3stat.<Nr> not registered' respectively 'program <hostname>.sapccmsr.<Nr> not registered'
    I am a little bit confused how to fix this. Can somebody help ?

    In the meantime I could solve the issue.
    The solution is that the registration command on TREX host had wrong parameters.
    I only have a pure TREX instance, no ABAP instance, no Java instance on the same host.
    In this case you have to register your agent at central SolMan system this way:
    sapccmsr -R pf=
    Don´t use the -j2ee parameter if you don´t have a java instance there.
    Please see the screenshot and the legend under:
    http://help.sap.com/saphelp_nw70ehp2/helpdata/en/e2/eff640fa4b8631e10000000a1550b0/frameset.htm

  • RFC issue in RAR 5.3 Risk Terminator

    Hi,
    We have RAR 5.3 with Risk Terminator configured. Since last couple of days, Risk Terminator is not working for one of our back end system.
    Getting below error message :
    "SAP Adapter has a problem, SOD violations will not be checked !!!
    Please check with your system Administrator
    Technical Info:
    senderAgreement not found: lookup of binding via CPA-cache failed for AdapterTyp"
    I have verified the configuration setting and confirmed below things:
    1. Config program do have RFC destination which is defined with registered program GRCRTTOCC5X
    2. The same program name is defined in the RAR connector with Outbount selected
    3. The SAP Adapter is Green. I have turned it off / on
    It was working well till few days back.
    Any suggestion would help a lot.
    Adeep

    Hi Deepak,
    Can you change your Program ID (GRCRTTOCC5X)  to any other name in your back end as well as RAR Report name  also.
    It will work.
    Regards
    Shiva.
    Edited by: Siva K Kumar on Jul 27, 2010 7:36 PM

  • Sender RFC Issue

    Hi All,
    I have an RFC-XI-File Scenario which is working fine in dev and qa. After moving to Pre-Prod, I see the inbound XML's do not have all the values. I debugged the program before the RFC call in R/3 and I see all the values. However when it come to XI there are only few values getting populated.
    I have restarted the channels but no luck.
    Please note that the scenario is working in Dev and QA and the IR objects / and ID objects are like.
    Please suggest solution
    Regards
    Unni

    However when it come to XI there are only few values getting populated.
    XI (normally) wont modify the input payload (unless mapping logic is applied).....are you able to see the entire message content in the log of your Communication Channel?
    Also there should not be any version conflict between the RFC in the SAP system and the RFC in XI/ PI
    Regards,
    Abhishek.

  • General issues during Installation

    Hi Experts,
    What are issues generally we are facing during installation of data sources  and loading of data in to DSO or Cube.(with real time example).
    and how that can be solved?
    Regards
    Tapashi saha

    Hi
    Discussed so many times.
    While installing the BC DS based on the Data flow  the error occurs, Normally the Shortdump if you select much Object at Grouping with Dataflow before after based on the time lines.
    The Connectivity / RFC issues between the systems
    The Data Init fails due to data inconsistencies.
    Hope it helps and clear

  • Strange response time for an RFC call viewed from STAD on R/3 4.7

    Hello,
    On our R/3 4.7 production system, we have a lot of external RFC calls to execute an  abap module function. There are 70 000 of these calls per day.
    The mean response time for this RFC call is 35 ms.
    Some times a few of them (maybe 10 to 20 per day) are way much longer.
    I am currently analysing with STAD one of these long calls  which lasted 10 seconds !
    Here is the info from STAD
    Response time :                10 683 ms
    Total time in workprocess : 10 683 ms
    CPU time  :                               0 ms
    RFC+CPIC time :                       0 ms
    Wait for work process           0 ms
    Processing time           10.679 ms
    Load time                            1 ms
    Generating time                   0 ms
    Roll (in) time                        0 ms
    Database request time         3 ms
    Enqueue time                      0 ms
    Number      Roll ins            0
                     Roll outs           0
                     Enqueues         0
    Load time   Program             1  ms
                      Screen              0  ms
                     CUA interf.          0  ms
    Roll time    Out                 0  ms
                      In                  0  ms
                    Wait                0  ms
    Frontend    No.roundtrips       0   
                      GUI time            0  ms
                      Net time            0  ms
    There is nearly no abap processing in the function module.
    I really don't uderstand what is this  10 679 ms processing time especially with 0 ms cpu time and 0 ms wait time.
    A usual fast RFC call gives this data
    23 ms response time
    16 ms cpu time
    14 ms processing time
    1 ms load time
    8 ms Database request time
    Does anybody have an idea of what is the system doing during the 10 seconds  processing time ?
    Regards,
    Olivier

    Hi Graham,
    Thank you for your input and thoughts.
    I will have to investigate on RZ23N and RZ21 because I'm not used to use them.
    I'm used to investigate performance problems with ST03 and STAD.
    My system is R/3 4.7 WAS 6.20. ABAP and BASIS 43
    Kernel 6.40 patch level 109
    We know these are old patch levels but we are not allowed to stop this system for upgrade "if it's not broken" as it is used 7/7 24/24.
    I'm nearlly sure that the problem is not an RFC issue because I've found other slow dialog steps for web service calls and even for a SAPSYS technical dialog step  of type <no buffer>. (what is this ?)
    This SAPSYS dialog step has the following data :
    User : SAPSYS
    Task type : B
    Program : <no buffer>
    CPU time                       0 ms
    RFC+CPIC time              0 ms
    Total time in workprocs    5.490 ms
    Response time               5.490 ms
    Wait for work process           0 ms
    Processing time             5.489 ms
    Load time                            0 ms
    Generating time                   0 ms
    Roll (in+wait) time                0 ms
    Database request time          1 ms ( 3 Database requests)
    Enqueue time                       0 ms
    All hundreds of other SAPSYS <no buffer> steps have a less than 5 ms response time.
    It looks like the system was frozen during 5 seconds...
    Here are some extracts from STAD of another case from last saturday.
    11:00:03     bt1fsaplpr02_PLG RFC     R     3     USER_LECKIT     13     13     0     0
    11:00:03     bt1sqkvf_PLG_18      RFC     R     4     USER_LECDIS     13     13     0     0
    11:00:04     bt1sqkvh_PLG_18      RFC     R     0     USER_LECKIT     19     19     0     16
    11:00:04     bt1sqkvf_PLG_18      RFC     R     4     USER_LECKIT     77     77     0     16
    11:00:04     bt1sqkve_PLG_18      RFC     R     4     USER_LECDIS     13     13     0     0
    11:00:04     bt1sqkvf_PLG_18      RFC     R     4     USER_LECDIS     14     14     0     16
    11:00:05     bt1sqkvg_PLG_18      RFC     R     0     USER_LECKIT     12     12     0     16
    11:00:05     bt1sqkve_PLG_18      RFC     R     4     USER_LECKIT     53     53     0     0
    11:00:06     bt1sqkvh_PLG_18      RFC     R     0     USER_LECKIT     76     76     0     0
    11:00:06     bt1sqk2t_PLG_18      RFC     R     0     USER_LECDIS     20     20     0     31
    11:00:06     bt1sqk2t_PLG_18      RFC     R     0     USER_LECKIT     12     12     0     0
    11:00:06     bt1sqkve_PLG_18      RFC     R     4     USER_LECKIT     13     13     0     0
    11:00:06     bt1sqkvf_PLG_18      RFC     R     4     USER_LECKIT     34     34     0     16
    11:00:07     bt1sqkvh_PLG_18      RFC     R     0     USER_LECDIS     15     15     0     0
    11:00:07     bt1sqkvg_PLG_18      RFC     R     0     USER_LECKIT     13     13     0     16
    11:00:07     bt1sqk2t_PLG_18      RFC     R     0     USER_LECKIT     19     19     0     0
    11:00:07     bt1fsaplpr02_PLG RFC     R     3     USER_LECKIT     23     13     10     0
    11:00:07     bt1sqkve_PLG_18      RFC     R     4     USER_LECDIS     38     38     0     0
    11:00:08     bt1sqkvf_PLG_18      RFC     R     4     USER_LECKIT     20     20     0     16
    11:00:09     bt1sqkvg_PLG_18      RFC     R     0     USER_LECDIS     9 495     9 495     0     16
    11:00:09     bt1sqk2t_PLG_18      RFC     R     0     USER_LECDIS     9 404     9 404     0     0
    11:00:09     bt1sqkvh_PLG_18      RFC     R     1     USER_LECKIT     9 181     9 181     0     0
    11:00:10     bt1fsaplpr02_PLG RFC     R     3     USER_LECDIS     23     23     0     0
    11:00:10     bt1sqkve_PLG_18      RFC     R     4     USER_LECKIT     8 465     8 465     0     16
    11:00:18     bt1sqkvh_PLG_18      RFC     R     0     USER_LECKIT     18     18     0     16
    11:00:18     bt1sqkvg_PLG_18      RFC     R     0     USER_LECKIT     89     89     0     0
    11:00:18     bt1sqk2t_PLG_18      RFC     R     0     USER_LECKIT     75     75     0     0
    11:00:18     bt1sqkvh_PLG_18      RFC     R     1     USER_LECDIS     43     43     0     0
    11:00:18     bt1sqk2t_PLG_18      RFC     R     1     USER_LECDIS     32     32     0     16
    11:00:18     bt1sqkvg_PLG_18      RFC     R     1     USER_LECDIS     15     15     0     16
    11:00:18     bt1sqkve_PLG_18      RFC     R     4     USER_LECDIS     13     13     0     0
    11:00:18     bt1sqkve_PLG_18      RFC     R     4     USER_LECDIS     14     14     0     0
    11:00:18     bt1sqkvf_PLG_18      RFC     R     4     USER_LECKIT     69     69     0     16
    11:00:18     bt1sqkvf_PLG_18     RFC     R     5     USER_LECDIS     49     49     0     16
    11:00:18     bt1sqkve_PLG_18     RFC     R     5     USER_LECKIT     19     19     0     16
    11:00:18     bt1sqkvf_PLG_18     RFC     R     5     USER_LECDIS     15     15     0     16
    The load at that time was very light with only a few jobs starting :
    11:00:08 bt1fsaplpr02_PLG RSCONN01                     B 31 USER_BATCH     39
    11:00:08 bt1fsaplpr02_PLG RSBTCRTE                     B 31 USER_BATCH     34
    11:00:08 bt1fsaplpr02_PLG /SDF/RSORAVSH                B 33 USER_BATCH     64
    11:00:08 bt1fsaplpr02_PLG RSBTCRTE                     B 33 USER_BATCH     43
    11:00:08 bt1fsaplpr02_PLG RSBTCRTE                     B 34 USER_BATCH     34
    11:00:08 bt1fsaplpr02_PLG RSBTCRTE                     B 35 USER_BATCH     37
    11:00:09 bt1fsaplpr02_PLG RVV50R10C                    B 34 USER_BATCH     60
    11:00:09 bt1fsaplpr02_PLG ZLM_HDS_IS_PURGE_RESERVATION B 35 USER_BATCH    206
    I'm thinking also now about the message server as there is load balancing for each RFC call ?
    Regards,
    Olivier

  • Error in RFC: Name of password is incorrect

    Hi All,
    I am using GRC AC 10.1 with SP06 and came across with one issue and so need your help to rectify it.
    I have created one cross system groups for all deveopement clients (SAP_DEV_CG) and put all the D-clients for all the landscapes.
    While running the risk violations reports on user level, i get to see the violations along with an error: "Risk analysis finished with error. Check log for details". SLG1 reports indicates that there is some issue with the RFC: Name or password is incorrect.
    The error is quite clear and self explanatory that there is some issue with the RFC; but my concern is that, as I  have put multiple development clients to this group so how would i know for sure that SLG1 indicates the RFC (password/name) issue to exactly what system. It will not be feasible to go and see all the systems one-by-one. I checked the logs in detail, navigated through all the technical information but not really able to see the particular system name where the real issue is there.
    Looking forward to your quick and positive response.
    Thanks,
    Ameet

    Hi Colleen,
    Thanks for your response and sorry for this delay in responding with your suggestions.
    SM21 results are as below, But I don't see any hints on the connector which is causing the error with RFC:
    Exeuting the jobs for each connectors or checking for each connectors one-by-one to investigate with the RFC issue is one option as I had already mentioend in my original post, but that would take quality time to come to one conclusion.
    Do we have any way out here to get this sorted out for the connector causing the error.
    Regards,
    Ameet

Maybe you are looking for