RFC not created in receiver system

Hi,
FIile-rfc received in receiver system until yesterday.now the RFC not reaching to receiver system.They are no changes and no change in RFC structure.
all the ques are clear and RFC connectin to the receiver system is alo fine and CC monitoring is also green and in the audit log everything is sucessful.sxmb?moni messages are sucessful.
please let me know where i can check ...
Regards,
hyma

Did you see any logs in receiver RFC channel?
Check the receiver service for interface in moni- SOAP header-Main document.
Also check if any conditions are specified in receiver determination.

Similar Messages

** File to IDoc scenario - IDoc not created in target system

Hi friends,
We are doing File to IDoc scenario. We made required setting in both application as well as XI system. While test the scenario, the file is picked up and successfully processed in SXMB_MONI, but the inbound IDoc is not created in target system. What could be the problem?
We are using DEBMAS message type DEBMAS06 IDoc type. We checked the following.
1) SM59 - Connections are OK both application and XI system
2) IDX1 - In XI System, we have assigned SAP<R/3> port.
3) IDX2 - IDoc is imported.
4) In ID - Sender File - Business Service - Adapter-Specific Identifier - Logical System name is given.
5) In application system. - Partner Profile maintained correctly.
6) SM58 - There is no error.
So, what could be the reason ?
Kindly reply, friends,
Thanking you.
Kind Regards,
Jeg P.

Hi,
Check all the steps ..
File to IDOC
Do these configurations in R/3 and in XI...
SAP XI
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
Thanks,
Satya

Requisition object not created in eRecruiting system

Dear Experts,
Please help. My eRecruiting system in production is having error at the moment. When recruiter approve Requsition form created by Manager (via MSS), the requisition object is not created in eRecruiting system.
The step by step scenarion:
1. Manager create Requisition Form in MSS - using PDF form.
2. Recruiter receive the form in Universal Work List (UWL) in HR Portal
3. Recruiter approve the form
4. Requisition form should be updated in eRecrutiing system : eRecruiting -> Requisition -> Maintenance, However, the object is not created.
Your help is appreciated!.
-Rahidah-

I have the same problem but the requisition is created in HRP5125 in SAP but does not reflect to portal any help on this will be appreciated.
Thanks,
Sheshu

Early watch alert task not created on satellite system via SDCCN

The task about EWA is not created on satellite system via SDCCN.
The RFC back was created on Solution Manager and the user assigned to it has the following profiles:
S_CUS_CMP (SAP_S_CUS_CMP) Read data
S_CMSREG (SAP_S_CSMREG) -> Central system repository data
S_BDLSM_READ (SAP_S_BDLSM_READ) -> SDCCN data
SAP_SV_FDB_NOTIF_BC_ADMIN -> Service Desk messages
SAP_SUPPDESK_CREATE -> Service Desk messages
I have checked the RFC authorizations and Connection nothing is wrong.
Do you folks have any clue about that issue?
tks,
Re

Hello,
Not really much information to go on. The Maintenance package tasks is intended to schedule the Refresh defintion and services SDCCN tasks. So is this tasks scheduled? Is this taks gettign any errors/warnings in the logs?
The EWA task is created when the refresh service task runs and gets a list of the serivce sessions that need to be
populated.
You can run a refresh services task to see if there are any sessions to pull. If ther are no sessions, it could be a problem in SMSY defintions for the system. if the system is not delared 100% correctly in SMSY you will not get an EWA session populated.
In DSWP in the SOlution is the EWA for the SID red flagged? If so this means the data still needs to be colelcted from the satellite/managed sysetm. Does the installation number of the SID match the one in SMSY? If not you willnot get any sessions.
Is the refresh session actually using the *BACK RFC to the intended Solution Manager ssystem and is it defined as the master in SDCCN RFC destinations?
If you go to SE37 and run TH_SERVER and specify the SM_SIDCLNTnnn_BACK RFC, does it pull the server list?
If so your back RFC is functioning properly and a logon is successful.
Are the service defintions being replaced successfully when the Maintenance Package runs? Are they replaced when an upgrade was done? It could be the service defintions need to be replaced.
But really more information is needed. I have covered off just some of the issues possible.
Regards,
Paul

EREC: Multipal IDOC are getting created in receiver system for one IDOC

Hello Experts,
I ran in to one wearied issue in IDOC creation in Receiver system. I am running PFAL in sender system for only Person but 10 IDOC are getting created in receiver system. I don't know why is this happening.
This issue started popping up after we ran RBDAPP01-Inbound Processing of IDocs Ready for Transfer. We ran this to change IDOC to 53 status. Now I don't know what went wrong but Perner distribution is behaving
Appreciate your help.
Regards,
Krishna Bidwai
Losangeles USA.
818 527 0204.

Yes, employee is getting created after adding 0003 into the filter, but can u please answer my another question, i.e. PERNR in sender and receiver system should be same.
So in Receiver system (ECC) do i need to maintain external number range for PERNR?
Thanks

Message not coming to Receiver system - File to RFC

I have a small problem in File to RFC connection. We are trying to create a PO using a BAPI. In the XI system , it shows the XML is processed successfully but PO is not generated in the R/3 system.
Is there any way to check whether the message has come to the receiver system. In fact we tried with a dummy insert command in a Z table . Even thats not happening. I thing the message is not at all coming to the receiver system, but the SXMB_MONI in Xi shows the message got processed successfully.
Do we need to make any settings in the Receiver system?

hi,
did you commit this bapi:
a) in the rfc adapter (in your communication channel) if you have sp14
b) in the bapi wrapper if you have < sp14 ?
https://websmp206.sap-ag.de/~sapdownload/011000358700000328352005E/HowtouseBAPandccBPM.pdf
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

RFC adapters are not reconnecting after receiver system shutdown

Guys,
we have some RFC adapters which connect to some systems which go through offline backup procedures during weekends.
The problem is that the RFC adapters which connect to these systems aren't able to recognize that these systems are already online, and they keep showing the communication channel as with error status (in communication channel monitoring).
If we go to the adapter and reactivate it, then it connects normally the receiver system and gets a no-error status. But there are quite a few adapters and it's not practical to perform this every monday. :/
Does anyone know what should I set to make the RFC adapters to retry the connection after a while?
Regards,
Henrique.

Shabarish,
thank you very much!
I hadn't noticed that one. :o)
Ideally I'd like a way of retrying automatically, and not just by demand. But I guess that's as good as it gets...
Thanks a lot,
Henrique.

RFC not shown in source systems

Hi All;
I create an RFC from BW to ERP 2004
now this rfc is being shown in transaction SM59 but when i run
transaction rsa1 and go to source systems there is no source system for the RFC that i created
Please help
Thanks and regards
Tushar

Tushar, it is not enough to just create an RFC connection in SM59. You also need to create a Source System connection in RSA1 that uses the RFC connection from SM59. Goto RSA1 and click on Source Systems. Right-click on Source Systems and Create. A window will appear prompting for the Source System type, use SAP System from Release 3.0E. It will then prompt you for Available Destination where you put in your RFC connection (it is a drop-down list). Type in your user-id and passwords to connect the two systems together and you are all set.
Your Source System will be set up. You can right-click on your Source System and select Check to verify the connections and the passwords.
Hope this helps.

ALE using HRMDA message type - Comit not perform in receiving system

Hi,
I want to use ALE to transfer HR master data between two ECC instances. I have set-up all the configuration; distribution profile, filter etc... I tried to transfer the master data using standard SAP report RHALEINI.
The iDoc is generated and transfer correctly in the receiving system. The final status of the iDoc is 53 - Application document posted. The issue we have is that the comit to tables is not happening. Infotypes remains empty even if the status of the iDoc says it was posted. We are trying to transfer infotype 0000, 0002, 0001 and 0006
Anyone can help ?....
Thanks
Louis

Hi Ted,
Thanks for your answer,
Autorization is the first thing that we consider. We generate the IDOC by the program RBDMIDOC .
The job's user is the sap_all authorization. So it should not related with auth.
And this does not always occur. For example, two days ago it occurs, but today does not occur.
Best Regards
Hasan.

Manual entries of TDS/TCS deduction not creating Challans in system

Hi All,
We are to pass the entries of TCS (tax collected at source) deduction from sales invoice through FI module. Since it is not possible to deduct the TCS from sales invoice automatically without SD module, we have decided to post the TCS deduction entries manually. But when we are posting these TCS entries manually system is not creating challans for these TCS entries.
Please guide me whether sustem will not create challans for manually decucted TDS / TCS entries?
Thanks in advance
Sonal

Hi,
tcs is not supported totally. u can deduct tcs from customer. for this in wht config setting u can activate wht for customer also from the path given below
SAP Customizing Implementation Guide > Financial Accounting (New) > Withholding Tax > Extended Withholding Tax > Company Code > Assign Withholding Tax Types to Company Codes
Warm Regards

CUA - Users not created in Central System

Hi - Just put in CUA into a Solution Manager 4.0 client - and have the following issue.
After performing SCUG - the users are brought into the central system BUT not created into the central system.
For example:
Child system is CLNT100
Parent system is CLNT200
In CUA - if I search on the user - I can see it exists in CLNT100, but no entry is created in CLNT200.
This is an issue as I can't use SU10 in CUA - to do mass changes as the users don't exist in this client.
I am pretty experienced with CUA - but have not seen this before - is there some new settitng that I need to make to create the users in the CUA client when performing SCUG?
Thanks

Hi - you only need to perform SCUG in the central system.
I have brought all the users accross from each child system.
I think I may have incorrectly analysed the error.
What I am trying to do is use SU10 in the Central system to make changes on users in the child systems. Issue is that none of the users that are in the child system only show up in SU10.
I therefore think that this is an issue with SU10 in CUA parent - as it is only picking up uses if they exist in this CUA parent client (i.e. not if they only exist in the child systems)
Is there any way to change the behaviour of SU10?

Issue:Creation of Extended iDOC data entries in receiving system.

Hi all,
I have extended standard IDOC MATMAS05 for classification view.I am receiving the data successfully on recewing side.And i have done coading in user exit to store data in database table inside
IDOC_INPUT_MATMAS01- function module.
When i execute the BD10 from sending sytem and view the idoc at receiving end from WE05 i can see the idoc but when i try to see the material i cant see the classification(extended) view in mm03.Rest of the views are created .When i execute the idoc from WE19 ,Classification(extended) view gets created.
Please guide me so that the CLASSIFICATION view get automatically created in receiving system without using WE19.
Thanks.

Yes i used this function module-
CALL FUNCTION 'BAPI_OBJCL_CREATE'
              EXPORTING
                objectkeynew            = objectkeynew1
                objecttablenew          = 'MARA'
                classnumnew             = wa_classnumnew1
                classtypenew            = z1sklart-klart              "classtypenew1
                status                  = '1'
STANDARDCLASS           =
CHANGENUMBER            =
                keydate                 = sy-datum
NO_DEFAULT_VALUES       = ' '
IMPORTING
CLASSIF_STATUS          =
              TABLES
ALLOCVALUESNUM          =
                allocvalueschar         = allocvalueschar2[]
ALLOCVALUESCURR         =
                return                  = return1
*WAIT UP TO 1 SECONDS.
            CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
             EXPORTING
               wait          = 'X'
IMPORTING
RETURN        =
Please explain me how to maintain the Views Status at MARA general info segment level.

Sapdata3 has been not created after Sap Neatweaver 7.3

Hi Gurus,
I have done the installation for SAP Netweaver 7.3 Java stack with distributed option with oracle database .
However file system created is sapdata1,sapdata2 , and sapdata4 has been created but sapdata3 is not created .
can any one susggest.
Regards,
Jeetendra

Hi Jeetendra,
Check whether you system is up and running ?
If yes, then sapdata3 is a folder created under /oracle/SID or /oracle based on your file system structure.
As right mentioned SAP installer will not create any file system. If file system /oracle/SID/sapdata3 is not available, SAP installer will create a folder sapdata3 under /oracle/SID and respective data files will be created under the same.
Hope this helps.
Regards,
Deepak Kori

BW and RFC problem -- Source system not created.

Hi Friends,
Before posting this post , i have searched so many posts and docs and but still got a problem in creation of R3 source sytem in BI7.0.
Steps i followed in R3 are as follws:
1) created alogical system for R3 and BI7.0
2)assigned this logical system to clients 001 and 800
001--Bi
800--r3
3)created user BWALEREMOTE in su01 with profile sap_all
Steps in BI7.0 are as follows:
1) Created logical systems for Bi and r3
2) assigned this logical systems to same clients
3) created user BWAleremote in su01 with profile SAp_ALL
with respect to RFC's
In R/3
SM59--created a RFC name same as logical system names
for R3 RFC destination-- user is BWaleremote, client is 800
for BI RFC destination -- user is Bwaleremote , client is 001
when i checked the connections , i can sucessfully test the connections , But remote logins are having problems.
r3 to BW is possible, but it is prompting the password for BI again
BW to R3 is not possible.
To my knowledge and search in forums,RFC connections are succesful, then it should not prompt for any passwords..so iam wrong
I also went into RSA!-- global settings-- i gave user as BWaleremote..
Plz help me in this
PAVAN

Hi Pavan,
The RFC configuration is probably wrong. Check the username/pswd that you are using to connect to the other system. Try logging normally through the sap logon pad using that username/pswd that you have mentioned in the logon tab in RFC connection entry. See if you are able to logon. In the remote logon, it should not ask for any password.
If this succeeds, then create the source system in RSA1 in the BI box.

RFC destination of receiver system

Hi Guys,
I am trying to do the shell creation from scracth, and now i have found on the RFC destination creation there are three RFC connection which needs to be define. But my question is in this step we dont have any receiver system becasue export files has not been generated yet that will come after this step, so how can i proceed.
Regards,
Subhash

Hello Subhash,
In the step 'Define RFC Destinations' you create the RFC destinations for the SAP systems that participate in your project (or subproject).
Yes, you are correct, since the target/receiver system is not yet created, you cannot establish a RFC for the same.
Please proceed by maintaining the following:
Server name, System number , Language, Client, Username and Password for the control and the sender system.
Best Regards,
Mridu.

RFC not created in receiver system

Similar Messages

Maybe you are looking for