Cleaning the queued calls in the outbound autodialer

Hi All;
In outbound auto dialer, I have a calls queued and I do not need to do outbound call for it, from where I can remove these calls to avoid trying to do outbound calls for it?
I tried to do delete for all the records existed in the database for the table of the campaign, but still the calls are coming, and I need to clean it, How? From where I can remove it.
Any help?
Regards
Bilal

Your kindly help is highly appreciated really.
Actually I did not get how to resolve my problem and finish from those records
About ur question why I decided not to call them: actually we migrated alot of data for testing, and they are bothering us, also it look like that we tried to cancel calling them by click on Reject, but it look like Reject does not remove them, but we need Reject Close. Am correct or not? By the way: maximum number of attempts has been placed 1, but really still the record come back even after we press on Reject button. Any advise? Does Reject Close resolve the problem?
But still I need to say that the dialer full by a lot of numbers, and keep pressing Reject is not a practical way, so how to remove them?
Do u mean I have to keep removing those records that has "P" for pending?
From the other side: we can not set a time to control when the record to be dead and no more need to dial it if was not dialed within specific time? From where to be set?
Regards
Bilal

Similar Messages

Need to know how to check the outbound queue in SAP for data flow into CRM

Hi Specialist's,
I have changed an entry in Customer Master Data in Sap r/3 and this change has come fine to CRM system.I checked the inbound BDOC in CRM ( Trn:SMW01) and it has come fine into CRM system.I am also able to see the affected field in CRM with new value.
I need to know how to check this from SAP side i.e. I have checked the outbound IDOC list (WE02) but could not find the record.
Is there any other way in SAP that i can check?
Also please let me know if there is any other way except IDOC in SAP to send data from R/3 to CRM?
Usefull answers will definitely be rewarded with points .
Thanks,
Abhinav.

Hi Abhinav,
There are no IDOCs generated in R/3 for replication. R/3 system calls BAPI and Function modules remotely on CRM system which are part of the Adaptors provided for middleware.
Try to deregister the outbound queues in R/3 (Transaction SMQS) and see if you get an entry in the Outbound Queue (Transaction SMQ1). I have not tried this.
If you don't get any entry in the outbound queue then definitely there would be some FM at R/3 end which would be calling CRM system remotely.
<b>Reward points if it helps.</b>
Regards,
Amit Mishra

How to make the outbound call in the CCA

HI everyone,
i have opened the CCA URL and they are agents and supervisor.now i want to make the outbound cal to the mobile no inside india.
when i make call i am getting this error "currently unable to reach the phone try again later"
and my port for TCPI bus "8888" is blocked for this reason i am getting this error
can any have the documents how the outbound and inbound cal are configured in the CCA
Please do the needful help
Regards
Laksh

That error means that the call center server thinks that it cant ring the agents phone.
The call center log file should show the cause.

District data missing in the Outbound Queue of CRM

Hi,
We have an issue with the information not flowing to the Outbound Queue of CRM.
For eg . When we change the District information for a BP and synchroniye the system, the information is flowing in the Inbound queue to the CRM system and we are able to find the District data in the Bdoc. But when we check the Bdoc in the Outbound queue of CRM for this site, this District information is missing over there.
Any pointers on this would be of great help.
Regards,
Rasmi.

Hi Rashmi
Which BDoc did you check - the MBDoc or the SBDoc?
I guess the first thing to do would be to see if the information is correctly updated in the CDB.
If the district is missing in the CDB entry then the problem is with the synchronisation between BUT000 and SMOKNA1
You may have already checked this but I just thought I would ask
James

How to Clean the Call Speakers - Lumia 920

This is a bad idea if you have a Lumia 920. Maybe you could try this on other phones but the quality of the Lumia 920 just pushes the dust around the inside of the phone and into the front camera somehow. I have had 3 Lumia 920 and the first two suffer from dust in the front camera which I think also affects the proximity sensor. I though that I was treating the phone wrong but it also happened to the windows store guy. There was an article on Windowsphonecentral.com about this and as for learning how to clean the speakers I would like to find out too.
Moderator's Note: A more appropriate subject was provided as this post was moved to the appropriate board.

You could use anti static cloth or compressed air to clean ive seen people using hoovers etc NOT ADVISABLE.
I would sent it to nokia care are its a known issue,it will be done under warranty.
If i have helped at all a click on the white star below would be nice thanks.
Now using the Lumia 1520

Idoc used by CRM to post the outbound delivery in R/3 while saving the sale

Hi,
Can any one tell me which idoc (from the r/3 system) the crm system calls while creating a inbound delivery for the sales order created in crm.
I am having fields like Transaction Type, Ext. Reference cust, Delivery Control etcwhich are there in the CRM.These fields need to copied to the R/3 in the tables LIKP and LIPS.
The process of creating the outbound delivery is automatic means when a sales order is created and saved in CRM ,the delivery is created in the R/3 (note: the order is not moved to r/3 ..Only delivery is created).
I need the idoc which is used by the CRM system to post the outbound delivery and any badi .so that I can extend the idoc segments and use the badi to populate the data.
Need your inputs on this.
Thanks in advance.
Regards
Shafath

Hi All,
For this requirement IDOC's are not used.Bapi is used.
The BAPI BAPI_DELIVERYPROCESSING_EXEC will be enhanced to add the new fields into the BAPI structure.
The BADI /SPE/BAPI_DLVEXEC_EX and the user exit EXIT_SAPLV50R_CREA_001 will be used to populate the data into the new fields created in the BAPI structure and the new fields added into the tables LIKP and LIPS.
Regards
Shafath

Custom fields in the outbound dialing list

Hi all. We use UCCX 7.1 Premium. I'm trying to set up the Outbound function. I need agents could see additional information about customer during an outbound call is proceeding. I can add a field of variables through the Desktop Admin interface but I can't understand how to fill this field by data from the dialing list e.g.
Does anybody know how to add such custom field to the dialing list?
Thanks.
k_rus

Hi,
See these related threadS:
Re: Replicating additional fields (R/3 4.7) to SRM product master
Transfer Inforecord Conditions Scales to SRM Product Master
https://www.sdn.sap.com/irj/scn/threadmessageid=6669812#6669812
Extending SRM Product Master
BR,
Disha

Creation of Inbound Idoc for the Outbound Idoc in same client

Hi,
My requirement:
Whenver an PO is created an Outbound IDOC is generated in system ABC with client 100.I want to pass this IDOC data to create an Inbound Idoc for Sales Order(SO) in the same client.
It would be helpful if anyone can answer on how to Transfer the Outbound Idoc after it crosses the port.
I found there is a field for function module in WE21,can this be used to get the requirement done.
Please suggest.
Regards,
Amar

Example of a program that create and post an inbound idoc....maybe that will help you:
report zzinbound_idoc.
data: g_idoc_control_record like edi_dc40 occurs 0 with header line.
data: g_edidd like edi_dd40 occurs 0 with header line.
data: g_e1bpache09 like e1bpache09.
parameter: mode type c default 'A'.
refresh: g_idoc_control_record, g_edidd.
clear:   g_idoc_control_record, g_edidd.
*-Build Control Record -*
g_idoc_control_record-mestyp = 'ACC_DOCUMENT'.   "Message type
g_idoc_control_record-idoctyp = 'ACC_DOCUMENT03'. "IDOC type
g_idoc_control_record-direct = '2'.              "Direction
* Receiver
case sy-sysid.
when 'DE2'.
    g_idoc_control_record-rcvpor = 'SAPDE2'.     "Port
    g_idoc_control_record-rcvprn = 'IDOCLEGACY'. "Partner number
endcase.
g_idoc_control_record-rcvprt = 'LS'.             "Partner type
g_idoc_control_record-rcvpfc = ''.               "Partner function
* Sender
g_idoc_control_record-sndpor = 'A000000002'.      "tRFC Port
case sy-sysid.
when 'DE2'.
    g_idoc_control_record-sndprn = 'IDOCLEGACY'. "Partner number
endcase.
g_idoc_control_record-sndprt = 'LS'.             "Partner type
g_idoc_control_record-sndpfc = ''.               "Partner function
g_idoc_control_record-refmes = 'Customer clearing'.
append g_idoc_control_record.
*-Build Idoc Segments -*
*---E1KOMG
clear g_edidd.
clear g_e1bpache09.
g_edidd-segnam               = 'E1BPACHE09'.
g_edidd-segnum               = 1.
move g_e1bpache09 to g_edidd-sdata.
append g_edidd.
*-Create idoc -*
*-Syncronous
if mode = 'S'.
call function 'IDOC_INBOUND_SINGLE'
    exporting
      pi_idoc_control_rec_40              = g_idoc_control_record
*     PI_DO_COMMIT                        = 'X'
*   IMPORTING
*     PE_IDOC_NUMBER                      =
*     PE_ERROR_PRIOR_TO_APPLICATION       =
    tables
      pt_idoc_data_records_40             = g_edidd
    exceptions
      idoc_not_saved                      = 1
      others                              = 2.
if sy-subrc <> 0.
    message id sy-msgid type sy-msgty number sy-msgno
            with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
endif.
*-Asynchronus
else.
call function 'IDOC_INBOUND_ASYNCHRONOUS'
    in background task as separate unit
    tables
      idoc_control_rec_40 = g_idoc_control_record
      idoc_data_rec_40    = g_edidd.
commit work.
endif.
write: / 'Well done!'.

Create Billing document automatically from the outbound delivery

Hi experts,
I'm not sure my client's requirement can be implemented but i'm posting this thread just in case someone have a suitable solution.
My client wloud like that billing documents (VF01) are created automatically when the outbound document (VL01N) is saved. He doesn't wont to perform an additional action, so the the custom transaction solution doesn't satisfy his requirement
Is there any solution to do this? (User Exit or Customizing)
Thanks

Hi,
One idea. You can do it with the userexit USEREXIT_SAVE_DOCUMENT in report MV50AFZ1. Here, you have the number of delivery. I suggest you to call a BAPI with a job created with the sequence of functions JOB_OPEN', 'GET_PRINT_PARAMETERS'
, 'RS_CREATE_VARIANT', 'JOB_SUBMIT'. 'JOB_CLOSE' with a gap of time (eg: 2 or 3 minutes). You can call a function IN UPDATE TASK in this function. (read Note 415716 - User exits in delivery processing), and in the coding of this function you can create the job and call a report with the BAPI (for instance, BAPI_BILLINGDOC_CREATEMULTIPLE). After, you can control the creation of invoices with tcode SM37.
I hope this helps you
Regards
Eduardo
PD: I forgot it. Control in which event you call the BAPI via job. I suggest you when you create the movement 601. You can do it with this coding:
    IF xvbuk-wbstk NE yvbuk-wbstk
    AND xvbuk-wbstk = 'C'.
       "code
    ENDIF.
Edited by: E_Hinojosa on Jan 21, 2011 9:15 AM

How write the Outbound file name in the Inbound file

Friends,
I have a scenario like this.
Outbout filename - sample.txt
In sample.txt, i have having data like 20
Inbound filename - vivek.txt
i need data the like sample, 20
(NOTE: sample is the outbound file)
How to get this scenario.
Thanks in advance.
regards,
Vivek.

Hi Vivek,
If your PI is of SP14 and more you have an option called Adapter Specific Message Attributes.(ASMA) in communicatoin channel configurtaion, Which will help you in capturing the Sender file name during runtime.
So you will have to enable that option (ASMA) in Commchannel and capture file name in UDF using Java Code with the help of sap related API and map it to the target field which u would like to get populated.
follow the thread it has the discussion about acessing the Source file name.
Re: Getting file directory using dynamic configuration:Code needed
Thanks,
Ram.

Please guide me how to do the Outbound Porcess in ALE

Hi Friends,
Kindly guide me on ALE/IDOC's step by step how to work on Outbound Process.
and the generated IDOC must be download & stored on the PC of the Sending System only in .txt file format.
so that the XI will collect that particular file in .txt format & upload it for Inbound process.
Thanks in Advance
Ganesh

IDoc Types:
IDoc type structure can consist of several segments, and each segment can consist of several data fields. The IDoc structure defines the syntax of the data by specifying a list of permitted segments and arrangement of the segments. Segments define a set of fields and their format.
An IDoc is an instance of an IDoc Type and consists of three types of records.
i. One Control record: each IDoc has only one control record. The control record contains all the control information about an IDoc, including the IDoc number, the sender and recipient information, and information such as the message type it represents and IDoc type. The control record structure is same for all IDocs.
ii. One or Many Data records: An IDoc can have multiple data records, as defined by the IDoc structure. Segments translate into data records, which store application data, such as purchase order header information and purchase order detail lines.
iii. One or Many Status records: An IDoc can have multiple status records. Status record helps to determine whether an IDoc has any error.
Message in IDoc Type:
A Message represents a specific type of document transmitted between two partners.
Outbound Process in IDocs:
Outbound process used the following components to generate an IDoc. A customer model, and IDoc structure, selection programs, filter objects, conversion rules, a port definition, an RFC destination, a partner profile, service programs, and configuration tables.
The Customer Model:
A customer model is used to model a distribution scenario. In a customer model, you identify the systems involved in a distribution scenario and the message exchanged between the systems.
Message control:
Message control is a cross application technology used in pricing, account determination, material determination, and output determination. The output determination technique of Message control triggers the ALE for a business document. Message control separates the logic of generating IDocs from the application logic.
Change Pointers:
The change pointers technique is based on the change document technique, which tracks changes made to key documents in SAP, such as the material master, customer master and sales order.
Changes made to a document are recorded in the change document header table CDHDR, and additional change pointers are written in the BDCP table for the changes relevant to ALE.
IDoc Structure:
A message is defined for data that is exchanged between two systems. The message type is based on one or more IDoc structures.
Selection Program:
Is typically implemented as function modules, are designed to extract application data and create a master IDoc. A selection program exists for each message type. A selection programs design depends on the triggering mechanism used in the process.
Filter Objects;
Filter Objects remove unwanted data for each recipient of the data basing on the recipients requirement.
Port Definition:
A port is used in an outbound process to define the medium in which documents are transferred to the destination system. ALE used a Transactional RFC port, which transfers data in memory buffers.
RFC Destination:
The RFC destination is a logical name used to define the characteristics of a communication link to a remote system on which a function needs to be executed.
Partner Profile:
A partner profile specifies the components used in an outbound process(logical name of the remote SAP system, IDoc Type, message type, TRFC port), an IDocs packet size, the mode in which the process sends an IDoc (batch versus immediate), and the person to be notified in case of error.
Service Programs and Configuration Tables:
The outbound process, being asynchronous, is essentially a sequence of several processes that work together. SAP provides service programs and configuration tables to link these programs and provide customizing options for an outbound process.
Process flow for Distributing Transactional Data:
Transactional data is distributed using two techniques: with Message control and without message control.
Process flow for Distributing Master Data:
Master data between SAP systems is distributed using two techniques: Stand alone Programs and Change Pointers.
Triggering the Outbound Process via Stand-Alone Programs:
Stand-Alone programs are started explicitly by a user to transmit data from one SAP system to another. Standard Programs for several master data objects exist in SAP. Ex. The material master data can be transferred using the RBDSEMAT program or transaction BD10.
The stand-alone programs provide a selection screen to specify the objects to be transferred and the receiving system. After the stand-alone program is executed, it calls the IDoc selection program with the specified parameters.
Triggering the Outbound Process via Change Pointers:
The change pointer technique is used to initiate the outbound process automatically when master data is created or changed.
A standard program, RBDMIDOC, is scheduled to run on a periodic basis to evaluate the change pointers for a message type and start the ALE process for distributing the master data to the appropriate destination. The RBDMIDOC program reads the table TBDME to determine the IDoc selection program for a message type.
Processing in the Application Layer:
The customer distribution model is consulted to make sure that a receiver has been defined for the message to be transmitted. If not, processing ends. If at least one receiver exists, the IDoc selection program reads the master data object from the database and creates a master IDoc from it. The master IDoc is stored in memory. The program then calls the ALE service layer by using the function module MASTER_IDOC_DISTRIBUTE, passing the master IDoc and the receiver information.
Processing in the ALE Interface Layer:
Processing in the ALE Layer consists of the following steps:
Receiver Determination: The determination of the receiver is done through Customer Distribution Model.
IDoc Filtering: if an IDoc filter is specified in the distribution model for a receiver, values in the filter are compared against the values in the IDoc data records. If a data record does not meet the filter criteria, it is dropped.
Segment Filtering: For each sender and receiver combination, a set of segments that are not required can be filtered out.
Field conversion: Field values in data records are converted by using the conversion rules specified for the segment.
Version change for segments: Segments are version-controlled. A new version of a segment always contains fields from the preceding version and fields added for the new version. Release in IDoc type field of the partner profile to determine the version of the segment to be generated.
Version change for IDocs: IDocs are also version controlled. The version is determined from the Basic Type field of the partner profile.
Communication IDocs generated: The final IDoc generated for a receiver after all the conversions and filtering operations is the communication IDoc. One master IDoc can have multiple communication IDocs depending on the number of receivers identified and the filter operations performed. IDoc gets the status record with a status code of 01 (IDoc Created).
Syntax check performed: IDoc goes through a syntax check and data integrity validation. If errors found the IDoc get the status of 26 (error during syntax check of IDoc Outbound). If no errors found the IDoc gets the status 30 (IDoc ready for dispatch ALE Service).
IDoc dispatched to the communication Layer: In the ALE process, IDocs are dispatched using the asynchronous RFC method, which means that the sending system does not await for data to be received or processed on the destination system. After IDocs have been transferred to the communication layer, they get a status code 01 (Data Passed to Port OK).
Processing in the Communication Layer:
To dispatch an IDoc to a destination system, the system reads the port definition specified in the partner profile to determine the destination system, which is then used to read the RFC destination. The RFC destination contains communication settings to log o to the remote SAP system. The sending system calls the INBOUND_IDOC_PROCESS function module asynchronously on the destination system and passes the IDoc data via the memory buffers.
you can use the file port in the partner profile to store the data in the application server.once it saved in the application server it cna be downloaded to the pc.

How to Debug the Outbound IDOC

Dear SDN Members,
How to debug the outbound idoc please.
Thanks in advance
Yerukala Setty

Hi,
IDocs are processed by a function module, which are mapped against in table EDIFCT. When you process an IDoc in transaction BD87 you can put a breakpoint in the function module and it will stop there.For outbound processing it depends on which program is sending the IDoc. For transactional data like purchase orders, the IDoc is created via RSNAST00 which in turn calls a function module assigned to the processing code (BD41).
Thanks,
Asit Purbey.

[svn] 1190: Clean the flex-sdk-description. xml during the clean stage of the build so the build starts from a "clean" state.

Revision: 1190
Author: [email protected]
Date: 2008-04-11 07:06:59 -0700 (Fri, 11 Apr 2008)
Log Message:
Clean the flex-sdk-description.xml during the clean stage of the build so the build starts from a "clean" state.
-Set the antTasks.compiled property if the flexTasks have already been compiled to avoid having a failure when calling ant main checkintests package
Modified Paths:
flex/sdk/branches/3.0.x/build.xml

Somewhere in your pom.xml where you are configuring your build dependancies there will be a line <scope>caching</scope> this line is configuring the build to use a flex runtime shared library. This line is generating the error because caching is not a valid dependancy scope in maven 3 however mojos uses it anyway. There was a defect opened against flexmojos; I've linked it below. Froeder's response to the issue was that it was not fixable, that the warning is expected and that we'll have to live with it for now.
https://issues.sonatype.org/browse/FLEXMOJOS-363?page=com.atlassian.jira.plugin.system.iss uetabpanels%3Achangehistory-tabpanel

Can I clean the clear ink head for mx7600 printer?

Clear ink tank indicator displayed so replaced it with genuine PGI-9 clear tank per instructions and same problem plus new B300 error code. Figured must've been bad new tank so ordered another and same problems. Ran all clean and deep clean utilities and then check nozzle pattern and same error message. Tried using warm water to clean the two male prongs that insert into the new tank per one suggestion as possible the ink heads had dried u and not allow clear ink into head(just a guess?) and still no luck.
Now reading about replacing "valve head"? Hate bring unit in for service as 3-5 years old and usually repair costs are more than just buying darn new printer which is silly as was working fine before the empty clear tank. Any input appreciated

Hi vacman,
Since you are receiving the B300 error, please turn off the printer and unplug the power cord from the power supply. After 5 minutes or more, plug the power cord of the printer back in, and then turn it back on. If the same error occurs, the printer will require servicing. Please call or email us at one of the methods on the Contact Us page to obtain your servicing options.
Did this answer your question? Please click the Accept as Solution button so that others may find the answer as well.

Cleaning the microprosessor on the logic board

hey guys,
I have an eMac 2002... I am trying to clean the heat sink and the microprocessor on my logic board so that I can apply new thermal paste. I heard to use 90% alcohol, anyone who tried it?
Another thing, I know this is for iMac and Mac minis but maybe some of you had an eMac before... There is a film on the microprocessor covering the whole square like a thin clear plastic one, does that come off before the new thermal paste or not?
And also my optical drive carrier again from the older eMac like all has a metal heat shield. The service manual calls for a cotter pin to hold it in place. I do not remember having a cotter pin there when I was disassembling it. However there is this plastic pin I found on the floor that may have popped without me noticing while I was taking it off. It looks like a screw but plastic without the threads instead a pop in type of kind. Any clues? Can this be the pin?

That film thing was on there... This is the first time I opened it and was kinda puzzled with it... It is like some small square plastic with a smaller square in the middle. I peeled it already being so curious. I think it was a unique thermal pad with the paste already on it like double sticky tape... Sides were covered with what looked like silver thermal paste and the inner square with a black looking paste... I know sounds crazy, but that is what is on my microprocessor...

Cleaning the queued calls in the outbound autodialer

Similar Messages

Maybe you are looking for