Creation of appointment, campaign,... generates ISP_D* queue
Hi all,
Does anyone has an idea why the system generates an ISP_D0000000000004 queue when an appointment, campaign, interaction log, ... is created.
And second question: is there a way to determine for which objects a queue is generated.
I thought the ISP_D queue was used to send stuff to the mapbox.
We do have a groupware site active for Lotus notes replication but there only appointments are replicated.
Little help, much appreciated.
Kind regards
Hello Tom,
Inbound ISP_D* queues will be created as a result of inbound CSA* queues which in turn are created whenever there's an edit made in activities, BPs etc.
After that filter conditions are read from table CMWC_MBA_FILTER which is mapped to the SPRO setting IMG under CRM->CRM Middleware and related Components->Server-Based Groupware Integration->Settings for Contacts (Business Partners)->Filter Condition for Business Partners Exchange with Groupware, and accordingly the data is sent to the Groupware site in the form of a queue ISP_OXXXXXXX.
The above example was taken for BPs, you can search for the spro settings for activities.
Hope that helps
Similar Messages
-
Automatic Activity Creation during the Campaign Execution
Hi Experts,
I have the following requirement.
If I run a campaign then a corresponding activity should be created in the CRM system.
Ex; If a mail Invitation to a Tradeshow is sent to 10 customers then 10 Activities should be created for each of the 10 Customers.
Does anyone know how to achieve this.
We are using SAP CRM 2007
Cheers,
ArunHi,
First create Activity Template for activity.
Under communication medium define followings:
Communication Medium: ZXXX - Email/Activities
Communication Methods and Transaction Types
Priority 7 - () Generate Contact - assign Transaction type (Activity Template)
Define Communication Methods for BP-Determined
3 Internet Mail (SMTP)
7 Generate Contact - assign Transaction type (Activity Template)
During Campaign creation under Channel you need to fill 'Email Form' assignment
also fill Activity template.
Once Campaign ready for execution, click on button, it will send email and also create activities using template for those BPs included in segment. -
Campaign generating appointments
Hi,
I have a scenario in which I must run a campaign (with communication medium: activity) that generates appointments with surveys attached to them. I am able to generate an appointment for each Business Partner in my target group, but appointments are generated all at the same time (which is specified in the activity template): I have in my Calendar all the appointments with the different BPs at the same date and time.
How can I generate appointments at different times for different BPs (e.g. an appointment every hour) through a campaign?
Thanks,
Laura.Hi, Sapan!
As I don't know all your requirements and possible constraints so I can't suggest you detailed solution but only general ideas.
The first is to build a segment, where the business partners will not add. E.g. one of the attributes may be something like: with no business transaction of type ZXXX, created for last month. This type of segment will require of you Business Intelligence Cube as data source.
May be simplier solution will be to code a function module and assign it to data source to make that business partners will not repeat in segment. There are three delivered in standard which are used for segmentation based on relationships, may be you will able to use them as some sort of example:
CRM_MKTTG_PF_BP_TAB_TO_CP
CRM_MKTTG_PF_BP_TAB_TO_CP_BW
CRM_MKTTG_PF_FIND_CPS
The second idea is to build automated marketing campaign. Where the action, as I can remember called "Create Target Group", will fill target groups.
In any case, this is a very interesting task, so hope that other more experienced experts give some advice.
Regards,
Andrey. -
Creation of production campaign and deletion of orders from campaign
Hi APO Gurus,
This is regarding campaign creation for a set or group of orders.
I have a group of orders in a z table, I want to create a campaign in PP/DS by using Heuristic : /sapapo/heur_pcm_create.
Can I do this without going to DS board, Simply by calling the above given function module in a z program?
Similarly , in another table if I have a set of orders , which are already part of a campaign.
Can I remove those orders from the Campaign by using heuristic : /SAPAPO/HEUR-PCM_Dissolve , without going to DS Board.
Waiting for your valuable suggestions.
Regards,
RaviResolved .
-
Creation of Appointment letter
Hi to all..
I have to Create Appointment letter for HR.For that I have Created Infotype 9001 and Standard Object for Appintment letter.But i m not getting how to use that infotypes and Standard object in Smartform for displaying that letter,
i have checked some module pools like MPXXXX01 were created by system.how to handle these
Please help me to understand the procedure for Creating Appointment letter..
Thanks in Advanced
SomnathHi Somnath,
I hope you have an idea about module pool programming as its based on the same.
Regarding the procedure steps
Create a infotype with some fields that u may want to show in the letter and want the end user to enter along with a field
of type PCLKEY
Now let the use enter the fields that can be captured in the letter. and when the use presses create letter the letter should appear
For this you may use function modules of sap script like INIT_TEXT , EDIT_TEXT inorder that the user edits the text directly.
After editing use when the person presses save you may call SAVE_TEXT.
And take the contents of the letter and save it in cluster with a key.
you may use the pernr/begda/endda/infotype/seqno for the key formation of the pclkey
and use import and export statements to export it to cluster.
You can also retrieve the letters from the import statement with the key stored in the infotype.
Regards,
Divya -
Creation of Table Maintainence Generator for Standard table
Hi,
I need to create a table maintainence generator for a standard SAP table.
The end user need have to delete certain entries from the table.
Is it viable to go for a table maintaninence generator or go for program which will delete the entry from the standard SAP table.
Which is the best method to go.
Thanks in Advance,
Irfan HussainHi,
But i think there is a differtent procedure to create a table maintainenece generator for the standard SAP tables than normal Ztables.
I thinl we need to take access key and do the modification.
Thanks in Advance,
Irfan Hussain -
Error: Unable to generate addon queue due to missing addons
Hi Team,
We're receiving this message error below in Configuration/BIND_PATCH phase of SAPEHPI when installing a EHP in ERP 6.0.
In log "SPDA_PATCHINT.LOG" I see the following entry
3WETN586 There are upgrades to required software component versions missing
3EETN581 Software component "LSOFE" rel."604" is required (see not "1143022")
3EETN584 Revise the selections and decisions in the phase IS_SELECT
2WETN586 There are upgrades to required software component versions missing
Solution to this error is given in note 1512309 and i already performed the steps given and regenrated XML file and also reset EHPI but still the error exist
Can you please let me know what needs to be done
Regards,
AbdulHi,
I am unable to paste the XML file here getting error "Your message exceeds the maximum length of 15000 characters".
Instead i have pasted the text file
[stack xml data: version=1.0]
[SPAM_CVERS]
SAP_APPL 604 0007
EA-APPL 604 0007
SAP_BS_FND 701 0007
EA-IPPE 404 0007
SAP_BASIS 701 0007
SAP_ABA 701 0007
SAP_BW 701 0007
PI_BASIS 701 0007
WEBCUIF 700 0007
ECC-DIMP 604 0007
FINBASIS 604 0007
SEM-BW 604 0007
EA-HR 604 0024
SAP_HR 604 0024
ERECRUIT 604 0007
EA-FINSERV 604 0007
IS-CWM 600 0017
IS-OIL 600 0017
IS-PS-CA 600 0017
EA-DFPS 600 0017
EA-PS 600 0017
EA-GLTRADE 600 0017
EA-RETAIL 600 0017
IS-M 600 0017
LSOFE 600 0017
INSURANCE 600 0017
IS-H 600 0021
IS-UT 600 0017
FI-CAX 600 0017
FI-CA 600 0017
SAP_AP 700 0019
[PRDVERS]
01200245450900000015SAP R/3 4.0B sap.com SAP R/3 4.0B -00000000000000
01200245450900000017SAP R/3 4.5B sap.com SAP R/3 4.5B -00000000000000
01200245450900000019SAP R/3 4.6B sap.com SAP R/3 4.6B -00000000000000
01200314690900000188SAP CATCH WEIGHT MANAGEMENT SAP IS-CWM 2.0 ON SAP ERP 2004sap.com SAP IS-CWM 2.0 ON SAP ERP 2004 -00000000000000
01200314690900000192SAP NETWEAVER 04 sap.com SAP NETWEAVER 04 -00000000000000
01200314690900000209SAP VERSORGUNGSADMINISTRATION SAP VADM 3.00 sap.com SAP VADM 3.00 -00000000000000
01200314690900000432SAP ERP ENHANCE PACKAGE 2005.2 sap.com EHP2 FOR SAP ERP 6.0 -00000000000000
01200314690900000463SAP ERP ENHANCE PACKAGE SAP ENH PACK 4 FOR SAP ERP 6.0sap.com EHP4 FOR SAP ERP 6.0 +00000000000000
01200314690900000866SAP NETWEAVER SAP EHP1 FOR SAP NETWEAVER 7.0sap.com SAP EHP1 FOR SAP NETWEAVER 7.0 +00000000000000
01200615320900000042SAP R/3 4.6C sap.com SAP R/3 4.6C -00000000000000
01200615320900000563SAP WEB AS 6.20 sap.com SAP WEB AS 6.20 -00000000000000
01200615320900000722SAP R/3 ENTERPRISE 47X110 sap.com SAP R/3 ENTERPRISE 47X110 -00000000000000
01200615320900001087SAP R/3 ENTERPRISE 47X200 sap.com SAP R/3 ENTERPRISE 47X200 -00000000000000
01200615320900001117SAP INSURANCE FS-CD 4.72 sap.com SAP INSURANCE FS-CD 4.72 -00000000000000
01200615320900001118SAP INSURANCE FS-CM 4.72 sap.com SAP INSURANCE FS-CM 4.72 -00000000000000
01200615320900001119SAP IS-M 472 sap.com SAP IS-M 472 -00000000000000
01200615320900001120SAP IS-T 472 sap.com SAP IS-T 472 -00000000000000
01200615320900001121SAP IS-U/CCS 472 sap.com SAP IS-U/CCS 472 -00000000000000
01200615320900001123SAP PATIENT MANAGEMENT 4.72 sap.com SAP PATIENT MANAGEMENT 4.72 -00000000000000
01200615320900001124SAP CAMPUS MANAGEMENT SAP IS-HER-CM 4.72 sap.com SAP IS-HER-CM 4.72 -00000000000000
01200615320900001125SAP PUBLIC SECTOR PSCD 4.72 sap.com SAP PUBLIC SECTOR PSCD 4.72 -00000000000000
01200615320900001127SAP INSURANCE FS-CS 4.72 sap.com SAP INSURANCE FS-CS 4.72 -00000000000000
01200615320900001134SAP OIL&GAS - IS-OIL SAP IS-OIL 4.72 sap.com SAP IS-OIL 4.72 -00000000000000
01200615320900001135SAP MINING - IS-MINE SAP IS-MINE 4.72 sap.com SAP IS-MINE 4.72 -00000000000000
01200615320900001220SAP DISCRETE INDUSTRIES SAP ECC DIMP 5.0 sap.com SAP ECC DIMP 5.0 -00000000000000
01200615320900001241SAP FI-CA 4.72 sap.com SAP FI-CA 4.72 -00000000000000
01200615320900001250SAP NETWEAVER 7.0 (2004S) sap.com SAP NETWEAVER 7.0 -00000000000000
01200615320900001251SAP ERP 2004 sap.com SAP ERP 2004 -00000000000000
01200615320900001284SAP WASTE AND RECYCLING 4.72 sap.com SAP WASTE AND RECYCLING 4.72 -00000000000000
01200615320900001296SAP ERP 2005 sap.com SAP ERP 6.0 +00000000000000
01200615320900001398SAP ERP ENHANCE PACKAGE SAP ERP VALUE PACK 2005.1 sap.com SAP ERP VALUE PACK 2005.1 -00000000000000
01200615320900001399SAP ERP ENHANCE PACKAGE 2005.1 sap.com EHP1 FOR SAP ERP 6.0 -00000000000000
01200615320900001469SAP ERP ENHANCE PACKAGE SAP ENH PACK 3 FOR SAP ERP 6.0sap.com EHP3 FOR SAP ERP 6.0 -00000000000000
[SWFEATURE]
1 01200615320900001296SAP ERP 2005 sap.com SAP ERP 6.0: SAP ECC Server
19 01200314690900000463SAP ERP ENHANCE PACKAGE SAP ENH PACK 4 FOR SAP ERP 6.0sap.com EHP4 FOR SAP ERP 6.0: Discrete Ind. & Mill Products
2 01200314690900000866SAP NETWEAVER SAP EHP1 FOR SAP NETWEAVER 7.0sap.com SAP EHP1 FOR SAP NETWEAVER 7.0: Application Server Java
26 01200314690900000463SAP ERP ENHANCE PACKAGE SAP ENH PACK 4 FOR SAP ERP 6.0sap.com EHP4 FOR SAP ERP 6.0: Financial Supply Chain Mgmt
30 01200314690900000463SAP ERP ENHANCE PACKAGE SAP ENH PACK 4 FOR SAP ERP 6.0sap.com EHP4 FOR SAP ERP 6.0: Central Applications
31 01200314690900000463SAP ERP ENHANCE PACKAGE SAP ENH PACK 4 FOR SAP ERP 6.0sap.com EHP4 FOR SAP ERP 6.0: Strategic Enterprise Mgmt
33 01200314690900000463SAP ERP ENHANCE PACKAGE SAP ENH PACK 4 FOR SAP ERP 6.0sap.com EHP4 FOR SAP ERP 6.0: Human Capital Management
46 01200314690900000463SAP ERP ENHANCE PACKAGE SAP ENH PACK 4 FOR SAP ERP 6.0sap.com EHP4 FOR SAP ERP 6.0: ERecruiting
48 01200314690900000463SAP ERP ENHANCE PACKAGE SAP ENH PACK 4 FOR SAP ERP 6.0sap.com EHP4 FOR SAP ERP 6.0: Financial Services
69 01200314690900000463SAP ERP ENHANCE PACKAGE SAP ENH PACK 4 FOR SAP ERP 6.0sap.com EHP4 FOR SAP ERP 6.0: EAM config control
9 01200615320900001296SAP ERP 2005 sap.com SAP ERP 6.0: SAP Learning Sol-Frontend ABAP
[SWFEATUREINC]
1 0120031469090000086619 01200314690900000463SAP NETWEAVER SAP EHP1 FOR SAP NETWEAVER 7.0sap.com SAP EHP1 FOR SAP NETWEAVER 7.0: Application Server ABAP +000000000000
1 0120031469090000086626 01200314690900000463SAP NETWEAVER SAP EHP1 FOR SAP NETWEAVER 7.0sap.com SAP EHP1 FOR SAP NETWEAVER 7.0: Application Server ABAP +000000000000
1 0120031469090000086630 01200314690900000463SAP NETWEAVER SAP EHP1 FOR SAP NETWEAVER 7.0sap.com SAP EHP1 FOR SAP NETWEAVER 7.0: Application Server ABAP +000000000000
1 0120031469090000086631 01200314690900000463SAP NETWEAVER SAP EHP1 FOR SAP NETWEAVER 7.0sap.com SAP EHP1 FOR SAP NETWEAVER 7.0: Application Server ABAP +000000000000
1 0120031469090000086633 01200314690900000463SAP NETWEAVER SAP EHP1 FOR SAP NETWEAVER 7.0sap.com SAP EHP1 FOR SAP NETWEAVER 7.0: Application Server ABAP +000000000000
1 0120031469090000086646 01200314690900000463SAP NETWEAVER SAP EHP1 FOR SAP NETWEAVER 7.0sap.com SAP EHP1 FOR SAP NETWEAVER 7.0: Application Server ABAP +000000000000
1 0120031469090000086648 01200314690900000463SAP NETWEAVER SAP EHP1 FOR SAP NETWEAVER 7.0sap.com SAP EHP1 FOR SAP NETWEAVER 7.0: Application Server ABAP +000000000000
1 0120031469090000086669 01200314690900000463SAP NETWEAVER SAP EHP1 FOR SAP NETWEAVER 7.0sap.com SAP EHP1 FOR SAP NETWEAVER 7.0: Application Server ABAP +000000000000
1 012006153209000012509 01200615320900001296SAP NETWEAVER 7.0 (2004S) sap.com SAP NETWEAVER 7.0: Application Server ABAP +000000000000
1 012006153209000012611 01200615320900001296SAP ECC 6.0 sap.com SAP ECC 6.0: SAP ECC Server +000000000000
2 012003146909000002209 01200615320900001296SAP LEARNING SOLUTION 6.00 sap.com SAP LEARNING SOLUTION 6.00: Training Management Frontend +000000000000 -
CIF Queues generated without active integration model
Hello All,
We are facing a unique issue, where queues are seen in SCM queue manager although those products are not there in any active integration model for transaction data.
The scenario is as follows:
1. We are CIFing only master data as we have only DP and release to R/3
2. There is active integration model for master data
3. There is no integration model for transaction data
However in SCM queue manager, I am seeing queues of type CFFCC "Location" "Product".
The function module name is /SAPAPO/CIF_IRQ_REDUCT_INBOUND.
We observed in R/3 that the goods movement transaction code MB1A is trigerring TRFC's which is generating the queues.
Has anyone encountered a similar scenario like this?
Regards,
KedarOi Jackeline!
Hello, all!
I think Vikas got the point, but let me be more specific...
The transfer of requirement reduction depended in previous releases (until PI 2002.1) only on an integration model for material master data being active. Then a new type of integration models was created to control the sending of requirement
reduction.
To activate the new logic a flag has to be set in customizing.
Use transaction /CFC9
OR
R/3 SAP Customizing Implementation Guide
-> Integration with Other SAP Components
-> Advanced Planning and Optimization
-> Application-Specific Settings and Enhancements
-> Settings and Enhancements for Requirement Reduction
-> Evaluate the Requirements Reduction Filter Object Type:
Then, flag 'Filter Object Requirements Reduction'
If you set this flag no queue of type CFFCC* will be sent if there is no explicit active integration model for Requirements Reduction. Please set this flag in production and delete any existing queues of type CFFCC*. No new such queues should be created in the future as long as you don't activate the transfer via an integration model.
I hope this information helps to clarify this issue.
Please give your feedback concerning the given solution.
Thank you!
Will -
Manually generate SAP Note queue in SNOTE
Hi!
I would like to know if it is possible to manually generate a queue of SAP notes in transaction SNOTE. Instead of importing one note after the other, I would like to generate a queue.
If this is possible, do you also know if SNOTE will determine the correct sequence of notes, and also if it will determine if there are any prerequisite notes for the notes I am importing?
Thanks.
Regards,
ThomasHi Olivier.
I am very familiar with support packages and SPAM, but thanks for the information anyway.
However, I don't see why being able to manually create short queues of notes is such a bad idea. After all, SNOTE itself automatically creates queues from time to time. Please see this link for information: [SAP Note Queue |http://help.sap.com/saphelp_nw70/helpdata/en/c3/0db13a95bed348e10000000a114084/frameset.htm]
-Thomas -
ABAP Client Proxy to File (File is not getting generated)
Hi All,
I'm trying out a scenario ABAP proxy --> XI --> FILE.
I have followed the given blog to create ABAP client proxy.
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
While executing the ABAP client proxy, the values are properly sent to XI and in the SXMB_MONI the message shows as successful. But the correspoding file is not created.
It seems everything is fine in the receiver adpater(Monitoring) and in the SXMB_MONI also the msg shows successful(receiver side).
The directory path and the corresping file creation parameters also looks fine.
Couldn't figure out what went wrong. Please help me on this.
Thanks,
Ajay.Hi Smitha,
Please find below the Call Adapter trace
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Adapter
-->
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="T">Party normalization: sender</Trace>
<Trace level="1" type="T">Sender scheme external =</Trace>
<Trace level="1" type="T">Sender agency external =</Trace>
<Trace level="1" type="T">Sender party external =</Trace>
<Trace level="1" type="T">Sender party normalized =</Trace>
<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
- <!-- ************************************
-->
<Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>
<Trace level="2" type="T">Request Line = POST /sap/xi/engine?type=entry HTTP/1.0</Trace>
<Trace level="2" type="T">Host = iscsapapp4w:8010</Trace>
<Trace level="2" type="T">Server protocol = HTTP/1.0</Trace>
<Trace level="2" type="T">Remote address = 10.191.117.166</Trace>
<Trace level="1" type="T">COMMIT is done by XMB !</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
- <!-- ************************************
-->
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
- <!-- ************************************
-->
<Trace level="3" type="T">XMB was called with external pipeline PID = ENTRY</Trace>
<Trace level="3" type="T">Getting type of XMB...</Trace>
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="2" type="T">XMB kind = CENTRAL</Trace>
<Trace level="3" type="T">Start pipeline found</Trace>
<Trace level="2" type="T">Switch to external start pipeline PID = CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV">
<Trace level="3" type="T">No triggers found. OK.</Trace>
</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">XMB entry processing</Trace>
<Trace level="3" type="T">system-ID = NW2</Trace>
<Trace level="3" type="T">client = 100</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = XIAPPLUSER</Trace>
<Trace level="1" type="Timestamp">2006-04-03T10:24:14Z CET</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- <!-- ************************************
-->
<Trace level="1" type="T">Message-GUID = B2DD6D78BBF141458DDC0DDE39782DE3</Trace>
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- <!-- ************************************
-->
<Trace level="3" type="T">QOS = EO</Trace>
<Trace level="3" type="T">Message-GUID = B2DD6D78BBF141458DDC0DDE39782DE3</Trace>
<Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
<Trace level="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
<Trace level="3" type="T">Generate prefixed queue name</Trace>
<Trace level="1" type="T">Queue name : XBTI0000</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTI0000</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="3" type="T">Setup qRFC Scheduler</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="3" type="T">Call qRFC .... MsgGuid = B2DD6D78BBF141458DDC0DDE39782DE3</Trace>
<Trace level="3" type="T">Call qRFC .... Version = 000</Trace>
<Trace level="3" type="T">Call qRFC .... Pipeline = CENTRAL</Trace>
<Trace level="3" type="T">OK.</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="3" type="T">Version number = 000</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!-- ************************************
-->
<Trace level="3" type="T">Persisting message Status = 001</Trace>
<Trace level="3" type="T">Message version 000</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
<Trace level="3" type="T">Trace object available again now. OK.</Trace>
<Trace level="3" type="T">Message was read from persist layer. OK.</Trace>
<Trace level="3" type="T">Message properties in XMB object were setup. OK.</Trace>
<Trace level="3" type="ToDo">Make sure we catch exceptions in persist read</Trace>
<Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
</Trace>
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- <!-- ************************************
-->
<Trace level="3" type="T">message version successfully read from persist version= 000</Trace>
<Trace level="2" type="T">Increment log sequence to 001</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="3" type="T">system-ID = NW2</Trace>
<Trace level="3" type="T">client = 100</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = XIAPPLUSER</Trace>
<Trace level="1" type="Timestamp">2006-04-03T10:24:14Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- <!-- ************************************
-->
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
<Trace level="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline attributes</Trace>
<Trace level="3" type="T">PID = SAP_CENTRAL</Trace>
<Trace level="3" type="T">ENABLE = 1</Trace>
<Trace level="3" type="T">TRACELEVEL = 0</Trace>
<Trace level="3" type="T">EXEMODE = A</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline elements</Trace>
<Trace level="3" type="T">ELEMPOS = 0001</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0002</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0003</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0004</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0007</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0008</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0009</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_RESPONSE</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="1" type="Timestamp">2006-04-03T10:24:14Z CET Begin of pipeline processing PLSRVID = CENTRAL</Trace>
- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
<Trace level="1" type="Timestamp">2006-04-03T10:24:14Z CET Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_RD_PLSRV</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">Start without given receiver</Trace>
<Trace level="2" type="T">Check conditions for rule line no. 1</Trace>
<Trace level="2" type="T">...valid Receiver w/o Condition: - ACN_LEGACY2_04_BS</Trace>
<Trace level="2" type="T">No Receiver found behaviour: 0</Trace>
<Trace level="2" type="T">Number of Receivers:1</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2006-04-03T10:24:14Z CET End of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 001</Trace>
<Trace level="3" type="T">Message version 001</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
- <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
<Trace level="1" type="Timestamp">2006-04-03T10:24:14Z CET Start of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_ID_PLSRV</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) ACN_LEGACY2_04_BS MI_Client_Proxy_Inbound</Trace>
<Trace level="2" type="T">...valid InbIf without Condition: MI_Client_Proxy_Inbound</Trace>
<Trace level="2" type="T">Number of receiving Interfaces:1</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2006-04-03T10:24:14Z CET End of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 002</Trace>
<Trace level="3" type="T">Message version 002</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" />
- <!-- ************************************
-->
<Trace level="1" type="Timestamp">2006-04-03T10:24:14Z CET Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_RECEIVER_SPLIT</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
<Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV" />
- <!-- ************************************
-->
<Trace level="3" type="T">Case handling for different plsrv_ids PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="2" type="T">got property produced by receiver determination</Trace>
<Trace level="1" type="T">number of receivers: 1</Trace>
<Trace level="1" type="T">Single-receiver split case</Trace>
<Trace level="1" type="T">Post-split internal queue name = XBTOM2__0001</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Persisting single message for post-split handling</Trace>
<Trace level="1" type="T" />
<Trace level="1" type="T">Going to persist message + call qRFC now...</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!-- ************************************
-->
<Trace level="3" type="T">Persisting message Status = 012</Trace>
<Trace level="3" type="T">Message version 003</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
<Trace level="3" type="T">Trace object available again now. OK.</Trace>
<Trace level="3" type="T">Message was read from persist layer. OK.</Trace>
<Trace level="3" type="T">Message properties in XMB object were setup. OK.</Trace>
<Trace level="3" type="ToDo">Make sure we catch exceptions in persist read</Trace>
<Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
</Trace>
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- <!-- ************************************
-->
<Trace level="3" type="T">message version successfully read from persist version= 004</Trace>
<Trace level="2" type="T">Increment log sequence to 005</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="3" type="T">system-ID = NW2</Trace>
<Trace level="3" type="T">client = 100</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = XIAPPLUSER</Trace>
<Trace level="1" type="Timestamp">2006-04-03T10:24:14Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- <!-- ************************************
-->
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
<Trace level="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline attributes</Trace>
<Trace level="3" type="T">PID = SAP_CENTRAL</Trace>
<Trace level="3" type="T">ENABLE = 1</Trace>
<Trace level="3" type="T">TRACELEVEL = 0</Trace>
<Trace level="3" type="T">EXEMODE = A</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline elements</Trace>
<Trace level="3" type="T">ELEMPOS = 0001</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0002</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0003</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0004</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0007</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0008</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0009</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_RESPONSE</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="1" type="Timestamp">2006-04-03T10:24:14Z CET Begin of pipeline processing PLSRVID = CENTRAL</Trace>
<Trace level="1" type="T">Start with pipeline element PLEL= 5EC3C53B4BB7B62DE10000000A1148F5</Trace>
- <Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST">
<Trace level="1" type="Timestamp">2006-04-03T10:24:14Z CET Start of pipeline service processing PLSRVID= PLSRV_MAPPING_REQUEST</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_MAPPING_XMS_PLSRV3</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV">
<Trace level="2" type="T">......attachment XI_Context not found</Trace>
<Trace level="3" type="T">Mapping is already determined in the interface determination</Trace>
<Trace level="3" type="T">Object ID of Interface Mapping 791955998E03380CA938A0130A348AFB</Trace>
<Trace level="3" type="T">Version ID of Interface Mapping 3475AE80930811DAA18DC14C0ABF75A6</Trace>
<Trace level="1" type="T">Interface Mapping http://accenture.com/xi101/ABAPclientProxy IM_Valuemapping</Trace>
<Trace level="3" type="T">Mapping Steps 1 JAVA com/sap/xi/tf/_MM_Valuemapping_</Trace>
<Trace level="3" type="T">Dynamic configuration is empty</Trace>
<Trace level="2" type="T">Mode 0</Trace>
<Trace level="3" type="T">Creating Java mapping com/sap/xi/tf/_MM_Valuemapping_.</Trace>
<Trace level="3" type="T">Load 3475ae80-9308-11da-a18d-c14c0abf75a6, http://accenture.com/xi101/ABAPclientProxy, -1, com/sap/xi/tf/_MM_Valuemapping_.class.</Trace>
<Trace level="3" type="T">Search com/sap/xi/tf/_MM_Valuemapping_.class (http://accenture.com/xi101/ABAPclientProxy, -1) in swcv 3475ae80-9308-11da-a18d-c14c0abf75a6.</Trace>
<Trace level="3" type="T">Loaded class com.sap.xi.tf._MM_Valuemapping_</Trace>
<Trace level="2" type="T">Call method execute of the application Java mapping com.sap.xi.tf._MM_Valuemapping_</Trace>
<Trace level="2" type="T">Java mapping com/sap/xi/tf/_MM_Valuemapping_ completed. (executeStep() of com.sap.xi.tf._MM_Valuemapping_</Trace>
<Trace level="3" type="T">Dynamic configuration is empty</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2006-04-03T10:24:15Z CET End of pipeline service processing PLSRVID= PLSRV_MAPPING_REQUEST</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 005</Trace>
<Trace level="3" type="T">Message version 005</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
- <Trace level="1" type="B" name="PLSRV_OUTBOUND_BINDING">
<Trace level="1" type="Timestamp">2006-04-03T10:24:15Z CET Start of pipeline service processing PLSRVID= PLSRV_OUTBOUND_BINDING</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_OUTBINDING</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV">
<Trace level="2" type="T">O U T B O U N D - B I N D I N G</Trace>
<Trace level="2" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">determine OUTBOUND BINDING for:</Trace>
<Trace level="2" type="T">-ACN_Sender_BS_XI</Trace>
<Trace level="2" type="T">-ACN_LEGACY2_04_BS</Trace>
<Trace level="2" type="T">http://accenture.com/xi101/ABAPclientProxy.MI_Client_Proxy_Inbound</Trace>
<Trace level="2" type="T">Channel found: - ACN_LEGACY2_04_BS - ValueMap_Repl_Receiver1</Trace>
<Trace level="2" type="T">no header mapping defined</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2006-04-03T10:24:15Z CET End of pipeline service processing PLSRVID= PLSRV_OUTBOUND_BINDING</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 006</Trace>
<Trace level="3" type="T">Message version 006</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
- <Trace level="1" type="B" name="PLSRV_CALL_ADAPTER">
<Trace level="1" type="Timestamp">2006-04-03T10:24:15Z CET Start of pipeline service processing PLSRVID= PLSRV_CALL_ADAPTER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
- <!-- ************************************
-->
<Trace level="3" type="T">Calling pipeline service: PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
<Trace level="3" type="T">ADRESSMOD = SD</Trace>
<Trace level="3" type="T">P_CLASS =</Trace>
<Trace level="3" type="T">P_IFNAME =</Trace>
<Trace level="3" type="T">P_METHOD =</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Unknown channel type: File</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = AENGINE</Trace>
<Trace level="3" type="T">ADRESSMOD = SD</Trace>
<Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_IE_ADAPTER</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- <!-- ************************************
-->
- <Trace level="1" type="B" name="CL_XMS_PLSRV_IE_ADAPTER-ENTER_PLSRV">
<Trace level="3" type="T">Channel for adapter engine: File</Trace>
- <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP">
<Trace level="2" type="T">return fresh values from cache</Trace>
<Trace level="2" type="T">Get logon data for adapter engine (SAI_AE_DETAILS_GET): af.nw2.iscsapapp4w</Trace>
<Trace level="3" type="T">URL = http://iscsapapp4w.idcsap.com:51000/MessagingSystem/receive/AFW/XI</Trace>
<Trace level="3" type="T">User = XIISUSER</Trace>
<Trace level="3" type="T">Cached = X</Trace>
<Trace level="3" type="T">Creating HTTP-client</Trace>
<Trace level="3" type="T">HTTP-client: creation finished</Trace>
<Trace level="3" type="T">Security: Basic authentication</Trace>
<Trace level="3" type="T">Serializing message object...</Trace>
<Trace level="3" type="T">HTTP-client: sending http-request...</Trace>
<Trace level="3" type="T">HTTP-client: request sent</Trace>
<Trace level="3" type="T">HTTP-client: Receiving http-response...</Trace>
<Trace level="3" type="T">HTTP-client: response received</Trace>
<Trace level="3" type="T">HTTP-client: checking status code...</Trace>
<Trace level="3" type="T">HTTP-client: status code = 200</Trace>
<Trace level="3" type="T">Deserializing message object...</Trace>
<Trace level="3" type="T">HTTP-client: closing...</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2006-04-03T10:24:19Z CET End of pipeline service processing PLSRVID= PLSRV_CALL_ADAPTER</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <!-- ************************************
-->
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 007</Trace>
<Trace level="3" type="T">Message version 007</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</SAP:Trace>
Thanks,
Jothivel. -
Campaign dates / call list dates
Hi,
What incidence is there on setting some dates in a campaign and others in my call list ?
I know that in the call list, the dates détermine the following :
Completed by : Date or time when call list should be completed by. If the call list is not completed by this date, it is considered overdue or past due.
Stop on : Date or time when processing should end for the call list. If no dates are specified, then the call list can be executed anytime.
Start on : Date or time when processing should begin for the call list. If no dates are specified, then the call list can be executed anytime.
But what if I created my campaign generating my call list on start/end dates that are different from the call list. Is there any repercussion? What do the campaign dates have effect on?
Thanks,
Eli
Edited by: Eli Finn on Mar 1, 2012 5:17 PMAnswer half tested :
If "Start planned" date in campaign creation is entered
=> it automatically sets the same date in the call lists in "start on"
If "End planned" date in campaign creation is entered
=> it automatically sets the same date in the call list in "completed by"
The dates can however still be changed in the call list section afterwards.
If anyone has any input on what other influence Campaign dates can have, would be welcome -
My client sent out an email campaign to 81 recipients. The campaign generated 25 hard bounces. Is there a way to get more detailed information about the reason for these bounces? We are trying to evaluate this result -- a high rate of hard bounces (over 30%) Your reporting does not provide much information.
Thank you.
CatherineHello Catherine,
Please submit a case if you haven't already on this so we can investigate further with the following details...
Site URL
Email campaign name
Is this happening with any other campaigns/sites?
If there is any specific domain emails for hard bounce, please mention that.
We'll may need to look into this further.
Thank you,
Sanjit -
Automatic/Direct Creation of Transfer OrderS
Hello Gurus,
these are my question:
(1)for Automatic/Direct Creation of Transfer Orders, should it be created when saving delivery order, or do I have to create transfer order after this function ? how to config this function?
thanks very much!Hi,
The concept of Transfer Order comes if the business have warehouse management system.
Once the delivery is created, we need to do picking.
This can be done in two ways
1. Manual Picking
This is done when there is no warehouse management. means in the delivery picking tab, you have a field as Pick Qty. The you have to give the quantity (either less than or equal to delivery qty field), then you can save the delivery. This is called manual picking
2. Automatic Picking
This is done when there is warehouse management is available. Then in the delivery picking tab, pick qty is grayed out. That means you cant enter the pick qty manually. For this you have to create a transfer order.
For this you have two options
1. With in the delivery:
In the delivery it self before saving the delivery, you can click on "subsequent functions" drop down list on the standard menu bar, in that you have option "Create Transfer Order" click on that
Then it will ask whether you want continue to next, say ok, then it will take you to Tranfer Order Creation Screen, Click on Generate TO item, and save it. Now the delivery is created and the Picking is done for that delivery.
2. Using Transaction Code
You can also do the same using transaction code. For this first you have to save the delivery.
Goto T. Code LT03, Then it will ask for
Warehouse Number (mandatory field)
Plant (optional no need to mention)
Delivery Number (mandatory field) and press enter
Then it will take you to Transfer order creating screen, which will be nothing but above mentioned screen. Continue with same process and save it.
Now picking is done for your delivery.
It cant be possible to create a Transfer Order automatically once after delivery is saved.
Hope this is clear.
Reward if helpful.
Thanks
Praveen -
How to Group messages in a same queue
Hi all,
if it's possible.... how can I group messages of a same interface in one only queue???
because today if SAP sends 100 iDocs, it generate 10 queues with 10 LUW each one... I want only one queue with 100 LUWs
I want it, even if the third message comes 10 minutes later and the queue is still being processed...
example....
my queue (Q1) has 2 luws being processed, and there's other queues with many other interfaces messages (Q2, Q3....Qn) and ten minutos later comes a third message wich should have to be on Q1... I don't want a new queue, I want the new message in queue(Q1) then i'll have sorted my three messages in only one queue
Any idea? thanksbecause today if SAP sends 100 iDocs, it generate 10 queues with 10 LUW each one... I want only one queue with 100
LUWs
There is an option of Queue Priritization (document available for the same in SDN)....using this you can make sure that all the message related to an interface are processed in a pre-defined queue only.
Check if this is what you are looking for.
Regards,
Abhishek. -
How to generate sales order number
Hai friends,
In sales order creation, I want to generate a sales order number (i.e., 1 for the first sales order, 2 for the second and so on). This number should be generated successively in background. How it can be done..?Hello,
Yes, I'm struggling to understand what you're after too. You could create a z table to keep track of the number if it's bespoke. Otherwise try these tables: FBN1, NRIV (intervals), T161 (po) TNRO (linked to NRIV).
Good luck!
Ash Thomas
http://www.ashthomas.com
Sap Abap Developer & Sap Abap Programmer
Maybe you are looking for
-
Help with multiple itunes accounts
Hello, I have multiple purchases from multiple apple id's on my devices. These were all legitimately my purchases; however, depending on the company I was working for, etc. I couldn't have my personal itunes on the company computers. I used older p
-
I did not choose "use icloud" option for storing during my initial setup. How can I reset icloud account, so it can be used for storing.
-
How do I log into the PC drive?
I work for a school district, and in order to access its server, IT configured the PC side so it is compatible. The problem is that when I boot to the PC, the log in screen is Press ctrlaltdelete I used the Mac combination, but of course the Help win
-
How can I dynamically change the currency symbol in reports using the LNNNGNNNDNN field format.
-
Last Scan Time vs Last Update Time
All, I have been using SW to track my Server 2003 boxes as MS will be EOL of these next week. In my Inventory report I include Last Scan and Last Update. As we migrate the boxes to Server 2012 - I had expected to see the 2003 Server OS drop off of t