Third Party (Garnishment) checks - RFC destination error

We have an issue with our testing of Third Party Garnishment checks. We have a split system, with our HCM system residing separately from the remaining ECC modules.
We are getting an error in regards to the printing of the checks in A/P.
The posting is working fine
the vendor account is cleared
However, It’s not creating a check # or check form.
We can do other check runs in this client fine; it’s just the 3PR runs that cause the error.
The text of the error message is as follows: An RFC destination could not be specified for the logical system HPQCLNT210.
We have exhausted our resources here looking into the RFC connection and the partner profile and we cannot find anything wrong with them.
Can someone offer suggestions on what else we could check? Thanks so much.

Hi David,
Did you check below is set-up correctly.
- Use transaction SM59 to create an RFC destinations for the remote system.
- Use transaction BD54 to create the logical system.
- Use transaction BD97 to link the RFC destination created in SM59 with the logical system created in BD54.
Also, check entries in TBLSYSDEST is filled with correct system name HPQCLNT210. Generally this error occurs when system name is incorrect in TBLSYSDEST.
Thanks,
Ameet

Similar Messages

RFC destination error in posting 3rd party payment in 4.7 FI system

Hi,
We are running in to a problem when we are processing a payment via transaction F110S in our R/3 4.7 system for Financials. We are integrating our Financial system with ECC6.0 for HCM. We receive 3rd party invoice from HCM successfully via ALE and post it in 4.7 system. When we try to process payment against this invoice, apparently 4.7 system is trying to communicate with ECC 6.0 system and issuing an error and the payment processing gets cancelled. It generates a clearing document with out a check.
The error says "An RFC destination could not be specified for the logical system HD1CLNT014
    Message no. B1550
Diagnosis
    An RFC destination should be specified for the logical system
    HD1CLNT014. This could not be done in this case. HD1CLNT014 is not your
    local logical system and this system is not included in the relevant
    Customizing tables.
Procedure
    Check:
        -   RFC destination
           -Port definition
         -oubound partner profile of message type SYNCH for this logical system
We checked our configuration for all Logical system and RFC destination and everything seems fine.
Any help in this regard is appreciated.
Thanks
Kesav

Hi David,
Did you check below is set-up correctly.
- Use transaction SM59 to create an RFC destinations for the remote system.
- Use transaction BD54 to create the logical system.
- Use transaction BD97 to link the RFC destination created in SM59 with the logical system created in BD54.
Also, check entries in TBLSYSDEST is filled with correct system name HPQCLNT210. Generally this error occurs when system name is incorrect in TBLSYSDEST.
Thanks,
Ameet

RFC destination error while importing a client request

Dear Experts,
We are trying to import a Client Export from our Prd system to Development System and we are unable to import the request as it pops up a RFC destination error.
We have checked the RFC in the Dev QAS and PRD related to TMSADM and all of them are working fine
FYI, We are able to release the transports from the development system and it can be moved till qas and prd . So the TMS Configuration is also good.
The data file and co file in the backend of development is the same size as that of the Prd system.
I am really stuck . Kindly suggest a solution . Please find the screenshots while importing
Regards,
Suratharajan .S

Hi Suratha,
Goto STMS->system overview and select the Communication tab.
Maintained the Instance number of the ASD system.
Once you maintained the instance number , you will able to see it in the RFC ASD.DOMAIN_ASD.
Also distribute the configuration after entering the instance number.
With Regards
Ashutosh Chaturvedi

Third party system (JCO) ---RFC--- PI ---RFC--- ECC

Hello all,
We are trying to implement the following scenario:
Third party system (JCO) -RFC-> PI -RFC-> SAP ECC
The third party system connect to PI via Java Connector API with a know user id in PI. After that third party system tries to obtain the RFC that is already implemented and remote enabled in SAP ECC environment. But at this step there is something wrong in third party system software because we are not able to obtain the RFC interface and metadata from PI repository.
1. This step is working correctly. Connection is OK.
            JCO.Client mConnectionPI = JCO.createClient("100", // SAP client
                                                                                "user_id", // userid
                                                                                "********", // password
                                                                                "pt", // language
                                                                                "10.x.x.x", // application server host name
                                                                                "01"); // system number
            mConnectionPI.connect();
2. This step is not working correctly:
            JCO.Repository repository = new JCO.Repository("TestRep", mConnectionPI);
            IFunctionTemplate ftemplate = repository.getFunctionTemplate("Z_RFC_XXX"); - not found exception
We would like to know if there is something missing in any environment that we have to configure or implement in order to fix this issue. Thanks a lot.

Hi Primini,
couple of stupid-but-necessary questions:
1) have you imported the RFC model in PI Repository?
You don't need to have the RFC metadata in PI ABAP stack (there is no point in doing that), but rather in the PI Repository/ESR, within the SWCV you've created.
Check the "Activities" session of this link for more details:
http://help.sap.com/saphelp_nw70ehp2/helpdata/en/2b/a48f3c685bc358e10000000a11405a/frameset.htm
2) if you have done 1), have you configured the RFC Sender scenario properly?
I mean, have you ran the configuration wizard to create the agreements & determinations, setting the RFC interface as both the sender and the receiver interface? Of course, the systems would be different: as the sender system, you'll have a Business Service representing the legacy/JCo system; as the receiver, you'll have the ERP Business System.
This should make your scenario work.
If it doesn't, try one more thing: in the JCo code, just for the metadata repository connection, use a connection to the ERP system. But for the actual call, use the PI system.
Let us know the results.
Best regards,
Henrique.

Third Party Tool-Open Hub Destination

dear all,
          can any one guide me as to how data(master data in particular) from bw can be transferred to oracle data base using open hub destiantion.is rfc connection between bw and third part tool enough,do we have to maintain the same structure in third party tool before executing DTP and how can this be done??
          i am now able to transfer data from bw into a flat file and also to data base (bw) and not aware of the this functionality-third party tool .any light thrown on this area is welcome and points will be awarded ,
thanks ,
sasidhar gunturu

Some light at the end of tunnel for sure...
Extraction to the third-party tool can be executed as follows:
       1.      You define an open hub destination with Third-Party Tool as the destination type.
       2.      You create an RFC destination for your third-party tool and enter it in the definition of the open hub destination.
       3.      You use API RSB_API_OHS_DEST_SETPARAMS to define the parameters for the third-party tool that are required for the extraction.
       4.      You either start extraction immediately or include it in a process chain. You can also start this process chain from the third-party tool using process chain API RSPC_API_CHAIN_START. The extraction process then writes the data to a database table in the BI system.
       5.      When the extraction process is finished, the system sends a notification to the third-party tool via API RSB_API_OHS_3RDPARTY_NOTIFY.
       6.      The extracted data is read by API RSB_API_OHS_DEST_READ_DATA.
       7.      The status of the extraction is transferred to the monitor by API RSB_API_OHS_REQUEST_SETSTATUS.
For more details click below -
http://help.sap.com/saphelp_nw2004s/helpdata/en/43/7a69d9f3897103e10000000a1553f7/content.htm
Hope it Helps
Chetan
@CP..

Force Third Party Availability Check

Hi,
can anybody help me force third party availability check for schedule line CS and item category TAS. I have tried to check the Availability in transaction VOV6, but without any success.
Thanks.

Hi,
Check Note 210417 - 'Check availability' for third-party orders. It looks AC can't be activated for third party item.
Regards

To check RFC destination

hello All,
Is there any function module available to check RFC destination is active or not?
Thanks,
Johnny

Hi Johnny,
You can use this FM RFC_VERIFY_DESTINATION if your release is greater than 4.6C.
Check this sample code from Craig Cmehil's weblog.
CALL FUNCTION 'RFC_VERIFY_DESTINATION'
EXPORTING
 DESTINATION = TMP
 TIMEOUT = 10
EXCEPTIONS
 INTERNAL_FAILURE = 1
 TIMEOUT = 2
 DEST_COMMUNICATION_FAILURE = 3
 DEST_SYSTEM_FAILURE = 4
 UPDATE_FAILURE = 5
 NO_UPDATE_AUTHORITY = 6
 OTHERS = 7.
IF SY-SUBRC EQ '0'.
 "* Do code here
ENDIF.
or you can also use this FM RFCPING and check this sample code from other thread.
DATA : IT_RFCSI LIKE RFCSI OCCURS 0 WITH HEADER LINE.
CALL FUNCTION 'RFC_PING'
DESTINATION IT_SLS-SYST
EXCEPTIONS
 SYSTEM_FAILURE = 1
 MESSAGE RFC_MESS1
 COMMUNICATION_FAILURE = 2
 MESSAGE RFC_MESS1.
IF NOT RFC_MESS1 IS INITIAL.
MESSAGE I000(YHPA0K) WITH RFC_MESS1.
ELSE.
CALL FUNCTION 'RFC_SYSTEM_INFO'
 DESTINATION IT_SLS-SYST
 IMPORTING
 RFCSI_EXPORT = IT_RFCSI
 EXCEPTIONS
 COMMUNICATION_FAILURE = 1
 MESSAGE MSG_TEXT
 SYSTEM_FAILURE = 2
 MESSAGE MSG_TEXT.
MESSAGE I001 WITH 'Connection to '(029)
 IT_SLS-SYST
 'Succeeded'(030).
ENDIF.
ENDIF.
Hope this will help.
Regards,
Ferry Lianto

Rollback work in third party system thru RFC

Hi Gurus,
Here is my scenario:
I am using RFC_UPDATE_TAXES_DOC to update records in third party system.
After successful updation only , I am calling BAPI_ACC_GL_POSTING_POST to post records into SAP.
Suppose I could post Taxes successfully into third party through RFC, but my BAPI gave me some error, I need to revert back the updation done in third party system as well.
Could you please suggest me an RFC which could do this or guide me with some pointers on how to achieve this.
Many Thanks,
Madan

Hi Primini,
couple of stupid-but-necessary questions:
1) have you imported the RFC model in PI Repository?
You don't need to have the RFC metadata in PI ABAP stack (there is no point in doing that), but rather in the PI Repository/ESR, within the SWCV you've created.
Check the "Activities" session of this link for more details:
http://help.sap.com/saphelp_nw70ehp2/helpdata/en/2b/a48f3c685bc358e10000000a11405a/frameset.htm
2) if you have done 1), have you configured the RFC Sender scenario properly?
I mean, have you ran the configuration wizard to create the agreements & determinations, setting the RFC interface as both the sender and the receiver interface? Of course, the systems would be different: as the sender system, you'll have a Business Service representing the legacy/JCo system; as the receiver, you'll have the ERP Business System.
This should make your scenario work.
If it doesn't, try one more thing: in the JCo code, just for the metadata repository connection, use a connection to the ERP system. But for the actual call, use the PI system.
Let us know the results.
Best regards,
Henrique.

Question on Third Party Payroll Check in XML Publisher

Hi:
I have created an XML Third Party Check report that is based on the queries found in the seeded Oracle PAYUSGAR.rdf 115.24 check report. The patch 9211869 fixed an issue in the standard report where multiple checks for the same employee to the same payee for the same amount were NOT printing the correct garnishment reference number. I have reviewed the report code but have not been able to fix this same issue through XML.
My queries will produce all of the correct data except the 2nd duplicate (same employee to the same payee for the same amount) prints the reference number from the 1st element rather than the 2nd. Does anyone know how the check data is tied to the elements through the tables?
My example is:
Person: Max Doe Check: 1234 Paid to: California Agency Check Amount: 121.00 Pre_payment_id: 766297 Ref # 4567
Person: Max Doe Check: 1234 Paid to: California Agency Check Amount: 121.00 Pre_payment_id: 766302 Ref # 657AA
(Ref # 657AA prints on the second check as Ref # 4567)
The query from the report is:
SELECT peev.screen_entry_value garn_ref_no
,:check_amount
,TO_CHAR(pay_us_payment_pkg.get_trx_date(
:business_group_id,
:ppa_payroll_action_id,
NULL,
:ppa_payroll_id,
:ppa_consolidation_set_id,
:ppa_org_payment_method_id,
:ppa_effective_date,
:ppa_date_earned,
:ppa_override_date,
ppp.pre_payment_id,
ppa.effective_date
),'DD-MON-YYYY') payment_date
,TO_CHAR(ppa.date_earned, 'DD-MON-YYYY')
,prr_att.run_result_id
,peef.entry_information2 -- FIPS code
,peef.entry_information3 -- Medical Indicator
,paa.assignment_action_id
,pet.element_type_id
FROM pay_element_entry_values_f peev,
pay_input_values_f piv_att,
pay_element_entries_f peef,
pay_run_results prr_att,
pay_run_results prr_pay,
pay_payroll_actions ppa,
pay_assignment_actions paa,
pay_action_interlocks pai,
pay_pre_payments ppp,
pay_input_values_f piv_pay,
pay_run_result_values prrv_att,
pay_run_result_values prrv_pay,
pay_element_types_f pet,
pay_element_types_f pet_calc,
pay_element_classifications pec
WHERE ROUND(ppp.VALUE ,2) = :check_amount
AND ppp.pre_payment_id = :pre_payment_id
AND ppp.assignment_action_id = pai.locking_action_id
AND pai.locked_action_id = paa.assignment_action_id
AND ppa.payroll_action_id = paa.payroll_action_id
AND ppa.action_type IN ('R', 'Q')
AND ((paa.source_action_id IS NOT NULL AND ppa.run_type_id IS NOT NULL) OR
(paa.source_action_id IS NULL AND ppa.run_type_id IS NULL))
AND ppp.personal_payment_method_id = peef.personal_payment_method_id
AND peef.assignment_id = paa.assignment_id
AND ppa.date_earned BETWEEN peev.effective_start_date
AND peev.effective_end_date
AND ppa.date_earned BETWEEN peef.effective_start_date
AND peef.effective_end_date
AND piv_att.input_value_id = peev.input_value_id
AND UPPER(piv_att.NAME) = 'ATTACHMENT NUMBER'
AND ppa.effective_Date BETWEEN piv_att.effective_start_date
AND piv_att.effective_end_date
AND piv_att.input_value_id = prrv_att.input_value_id
AND prrv_att.result_value = peev.screen_entry_value
AND prrv_att.run_result_id = prr_att.run_result_id
AND paa.assignment_Action_id = prr_att.assignment_Action_id
AND prr_att.element_type_id = peef.element_type_id
AND peef.element_type_id = pet.element_type_id
AND pet.classification_id = pec.classification_id
AND pec.classification_name = 'Involuntary Deductions'
AND pec.legislation_code = 'US'
AND pec.business_group_id IS NULL
AND fnd_number.canonical_to_number(pet.element_information5) = pet_calc.element_type_id
AND pet_calc.element_name LIKE pet.element_name || '%Calculator'
AND pet_calc.element_type_id = piv_pay.element_type_id
AND NVL(ppa.date_earned, ppa.effective_date) BETWEEN piv_pay.effective_start_date AND piv_pay.effective_end_date
AND piv_pay.input_value_id = prrv_pay.input_value_id
AND UPPER(piv_pay.NAME) = 'PAY VALUE'
AND fnd_number.number_to_canonical(ppp.VALUE) = prrv_pay.result_value
AND prr_pay.run_result_id = prrv_pay.run_result_id
AND prr_pay.assignment_action_id = paa.assignment_action_id
AND prr_pay.element_type_id = pet_calc.element_type_id
ORDER BY prr_att.run_result_id;
Somehow, Oracle has fixed this in the rdf but I have not been able to figure out how exactly. This is a function call in the report but they are passing the check amount and the prepayment_id. Regardless of which pre_payment_id is sent in, 2 rows are returned.
If anyone has any thoughts, please let me know. This is the final tweak that is stopping our go-live with this.
Thanks, RL

In bug 6779249 it states that third party checks are not supported for XML...
But, as we have bought into the push to convert we now are down to payroll checks and third party checks to get our company off of Optio once and for all...
Other than attempting to write a complete custom process from scratch (just to throw out next year when we upgrade to 12) does anyone have any solutions to getting 3rd party checks to print with BIP in Oracle Applications (11.5.10)?
Scott

RFC destination error in SM58

Hi,
We are getting an error in SM58 "P85040 does not exist".
What could be the reason for this error in PI system?
When I checked, there is no RFC destination configured with the name P85040. Also there is no communication channel configured with the RFC destination parameter P85040.
Kindlly help.
Thanks,
John

Hi John,
The reason can be the host name you are assigning is not existing.
In RFC destination the host name is for that particular client which is pointing to IP address not to the logical system. You can choose name of RFC destination same as of your logical system.
You can get the host name by login to SAP system and the using MENU ... System->Status and in lower right corner you can find it.
Sachin
Edited by: Sachin Dhingra on Dec 18, 2008 1:18 PM

** End-to-End Monitoring - RFC destination error while save config in RWB

Hi Friends,
We have 2 RFC destinations in our XI server. 1) PMI<client>001 2) PMI<client><client>800. First one is for XI server. Next one is for Sender/Receiver System.
We want to activate End-to-End Monitoring in RWB. For this, when I save configuration, it throws the following error.
Incorrect RFC Destinations: When the configuration is saved, an RFC destination is created on the monitoring server for each XI component to enable end-to-end monitoring of the respective XI component. However, the test call failed for the destinations listed. Therefore, you must check the call and the authorization on the monitoring server for the destinations concerned, by using transaction SM59. Also check whether RFC user used for the destination is maintained in the relevant XI component. Note that a component can only be monitored when its RFC destination is maintained correctly.
I have checked the user in the above destinations. For the first destination, we have assigned PIRWBUSER of XI system. Test Connection is OK, but unable to login remote. At the same time, PIRWBUSER is not locked.
For the second destination, I have assigned some login user of sender/receiver system. Test connection is OK. Able to login remotely.
There is no RFC user in our XI system. (I tried using RFCUSER* thru SU01 tcode).
There is no PIRWBUSER in the Sender/Receiver System.
In RWB, Configuration, 3 components are there. 1) XIIntegrationServer 2) Business System (for Sender/Receiver System) 3) XI Adapter Framework. I selected last two. (First one is already selected). Monitoring Level : Medium (for all 3). Send and Receive Check box is selcted for the last two.
So, what could be the problem for the above error?
Could you kindly clarifiy friends.
Thanking you
Kind Regards,
Jeg P.

Hi friends,
I have one RFC Destination PMI<sysid>001. (Abap Connction) in my XI system. This destination is for XI server. Connection Test is OK. Remote Logon by using the PIRWBUSER is also ok.
In the 'Configuration' tab of the Runtime Workbench, when we select 'Save Configuration', (Business System and Adapter Framework is not activated) with the default activation for XI Integration Server, the system throws the following error.
Incorrect RFC Destinations: When the configuration is saved, an RFC destination is created on the monitoring server for each XI component to enable end-to-end monitoring of the respective XI component. However, the test call failed for the destinations listed. Therefore, you must check the call and the authorization on the monitoring server for the destinations concerned, by using transaction SM59. Also check whether RFC user used for the destination is maintained in the relevant XI component. Note that a component can only be monitored when its RFC destination is maintained correctly.
When we save configuration, an one more destination is automatically created in the name as below.
PMI<sysid>001<yyyymmdd>. For Example, PMIPID00120080207.
When we test newly created RFC destination, connection is OK, but not able to remot login using the same user PIRWBUSER.
The difference between old and new RFC destination, in old, we have selected Load Balancing is 'Yes', but in the new it is 'No'. The system also tells the error below.
Name or Password is incorrect (repeat logon) - PMIPID00120080207
But, still remote login is possible in the old RFC destination using the PIRWBUSER.
So, What could be the problem ...?
Kindly reply, friends.

Interface RFC destination Error

Hi, while testing our interfaces we get this error, Stack>Error: Transaction IDX1: Port HED_020, client , RFC destination contain errors
We have checked IDX1 and SM58/59 and cant find any error.
Has anybody come across this before?
Thanks

Where do you get this error? In MONI or in SM58?
Make sure that the User Id in the RFC destination has the authoizations to post Idoc's.
Make sure that the receiver Idoc adapter has a valid Port name and RFC destination values as created in IDX1 and SM59
Regards
Bhavesh

RFC DEstination Error

After creating the Destination in sm59 I tested the connection.
When testing the connection, it gives the result as
Connection type: R/3 connection
Logon: 2 msec
 0 KB: 0 msec
10 KB: 1 msec
20 KB: 1 msec
30 KB: 1 msec
I'm trying to create a rfc destination to php in the same system with the same hostname in which SAP is also running...I'm working with ides.
but when I try to run my php file inside sapclasses in www directory it gives an error as
SAPRFC extension not loaded
Message: This script use SAPRFC extension module for PHP and the extension isn't loaded. You can download it with installation instructions from http://saprfc.sourceforge.net. If you have already the extension compiled and installed, check your php.ini configuration

Here's a full text of the error I receive
Error when processing your request
What has happened?
The URL http://<host_server>.com:<port>/sap/bw/BEx was not called due to an error.
Note
The following error text was processed in the system BQ1 : com.sap.engine.services.rfcengine.RFCException: Incoming call is not authorized
The error occurred on the application server <host_server> and in the work process 0 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Form: IF_RSRD_F_DISTRIBUTOR_RT~DISTRIBUTE of program CL_RSRD_DISTRIBUTOR_KM========CP
Form: EXECUTE_NODES of program CL_RSRD_SETTING===============CP
Form: EXECUTE_NODES of program CL_RSRD_SETTING===============CP
Form: EXECUTE_NODES of program CL_RSRD_SETTING===============CP
Form: EXECUTE of program CL_RSRD_SETTING===============CP
START-OF-SELECTION of program RSRD_BROADCAST_PROCESSOR
What can I do?
If the termination type was RABAX_STATE, then you can find more information on the cause of the termination in the system BQ1 in transaction ST22.
If the termination type was ABORT_MESSAGE_STATE, then you can find more information on the cause of the termination on the application server <host_server> in transaction SM21.
If the termination type was ERROR_MESSAGE_STATE, then you can search for more information in the trace file for the work process 0 in transaction ST11 on the application server <host_server>. In some situations, you may also need to analyze the trace files of other work processes.
If you do not yet have a user ID, contact your system administrator.
Error code: ICF-IE-http-c:100-u:COLLINS -l:E-s:BQ1-i:<host_server>_BQ1_00 -w:0-d:20051012-t:121010-v: RABAX_STATE-e:CALL_FUNCTION_REMOTE_ERROR
HTTP 500 - Internal Server Error
Your SAP Internet Communication Framework Team

Checking RFC destination availability

Hello,
In a transaction I'm working on, I loop at a table containing RFC destinations, and I call the same function module on each of these destinations. What I would like to do is, prior to the call, test if the system behind the RFC destination is available (neither completely crashed, nor just blocked by an administrator).
I tried to do this by simply calling any BAPI on the remote system, and check if there was a connection error. But the problem is, if the system is not down but just blocked by an administrator, the transaction suddenly displays the logon page of the remote system.
Do you know of a simple way to do this ?
Thanks in advance.

Hello Thomas
You could try with asynchronous RFC calls (for details refer to the ABAP documentation of CALL FUNCTION).
Asynchroner RFC
2. CALL FUNCTION func STARTING NEW TASK task
                [DESTINATION {dest|{IN GROUP {group|DEFAULT}}}]
                parameter_list
                [{PERFORMING subr}|{CALLING meth} ON END OF TASK].
Regards
Uwe

RFC destination error in transport

Hello,
We are trying to import a transport into our BW QA system and we keep getting return code 8 with the following text:
BW RFC destination <systemname> is not maintained in the source system
Message no. R3078
The transport contains cubes and three ODSs. After the transport fails and I check the QA system, the cubes are active, but the ODSs are not.
I searched SDN and found another thread explaining the same problem and I tried everything suggested there. I looked in RSA1 --> Mapping of the source system names, and the BW DEV and QA systems are listed. I also looked in SM59 and checked the RFC connection, and that is ok as well.
Does anyone have any suggestions?
Thanks
Charla

I have searched OSS further and found that the contents of my RSLOGSYSDEST table are off.
The contents are as follows:
Src System RFC Destination
AWQ100 AWP100
QAT100 QAT
I believe that in the above table, the AWP100 should be AWQ100. I looked at this table in our production environments, and in those cases the Src system entry and RFC Destination entry are the exact same, so I think this should be the case in our AWQ100 system as well.
Just curious if anyone knows if there is a program I can use to modify this table.
Thanks
Charla

Third Party (Garnishment) checks - RFC destination error

Similar Messages

Maybe you are looking for