Identify record number being processed in Custom Integrator?

Hi gurus,
We have developed a custom integrator using a PL/SQL packaged procedure as the interface. Inside this package we insert into a custom table.
We are on Oracle Financials 11.5.10.2.
The custom table is located in a custom schema called CGL.
Our requirement is to perform some validation in the database package when the Web ADI infrastructure is processing the first row in the excel spreadsheet that the user is using to upload data.
We have a header row with the following columns.
Source System
Feeder System
Version Number
When the user chooses Oracle => Upload option from the Excel menu, we have to validate that the Version Number is valid i.e. we have to validate that the previous version of the file for the Source System and Feeder System combination has been successfully processed by the subsequent programs before the user is allowed to upload the next version of the file for this combination.
Our requirement is to perform the validation when row number 1 is being processed. However, I have not been able to find any documentation that allows us to identify the record number in PL/SQL.
Alternately, is there an environment variable or some other way to populate row numbers in excel spreadsheets being downloaded using the template so it can be passed to the package and used to identify the row being processed.
Any help in this regard will be greatly appreciated.
Venkat

Hi Venkat,
Would you give a try with the following option:
Define a column in your layout, and set the default type to formula and enter an excel formula like
=IF(ISBLANK(C7);"";ROW()-ROW($B$6))
This function should put a number into the column and it should start with one, followed by 2,3 etc. The 7,C,B,6 needs to be set according your layout. I hope you can manage this.
Assuming your sheet has 100 lines, you shall have then a 1-100 in this column. I would secure this column, read only flag in the layout.
Any further explanation needed? Just replay here.
br, Volker

Similar Messages

Controlling number of records to be processed

Hello -
I have a procedure which eventually processes about 100 records. Our team wants to process only 50 records at a time. And they want to look at the 50 before being processed.
Procedure functionality is as follows:
- cursor fetches all qualified records for the process (100)
- creates record in order header and detail tables for all the qualified records
- then, checks for another criteria
- creates another detail record for the same header record
I have tried 'where rownum < 50' at the cursor itself. But, it anyways is processing all 100 records when it is creating records into orders tables.
Could you please suggest how I can select and process only those particular 50 orders? Thanks,

Thanks for the response.
I am essentially generating an excel spread sheet of records that are part of the first batch and sending them out. But, when I try to execute the complete procedure, it is executing all of them in one single batch.
Here is how my code is...in its simplified format:
PROCEDURE p_r_1 IS
p_ref_cur package.p_ref_cur;
CURSOR c1 IS
SELECT max(sal)
FROM emp
WHERE deptno = 20;
c_eligible_rec c1%rowtype;
v_sal emp.sal%TYPE;
v_test number := 0;
BEGIN
OPEN c1;
LOOP
FETCH c1 INTO c_eligible_rec;
EXIT WHEN c1%NOTFOUND;
OPEN p_ref_cur FOR
SELECT grade
FROM salgrade
where v_sal >= losal and v_sal <= hisal;
LOOP
FETCH p_ref_cur INTO rec;
v_test := rec.sal;
EXIT WHEN p_ref_cur%NOTFOUND;
END LOOP;
close p_ref_cur;
dbms_output.put_line(v_test);
END LOOP;
END;

Re:'Delivery number is currently being processed by user

Hi,
I am creating new delivery based on sales order and assiging craeted delivery to shipment using VL01N and VT01N.Some times getting error as 'Delivery number is currently being processed by user'. I am using synchrounus
update in BDC.
Can i use 'Commit work and Wait' along with synchrounus update in BDC?
To avoid this error message is there any alternate solution.
Regards,
Suresh Kumar.

i have had the same issues, and niether synchronous update, nor commit and wait work in all cases.
an option would be to enqueue the delivery in between the two steps.
create the delivery, then enqueue the delivery (LIKP, i think) with a wait code on it. the system will wait until the first process releases the lock on the delivery and then give it to you. The lock will be discarded when you do a commit after second step, but for readability, i always dequeue.
this is what we do, and i cannot guarantee it will work for you.

Contracts - 'Document still being processed in the background; try again la

Hello,
When trying to make adjustments to multiple contracts we are receiving the error message 'Document is still being processed in the background; try again later.' We have tried again later to no effect.
Ultimately, this means that these contracts (30 altogether) cannot be altered in anyway i.e. held, deleted, released, approved and it means that they just sit there.
This also has implications when raising another contract to replace these contracts. For example if you want to use the same vendor this will cause great confusion for our users when trying to select the correct correct to spend money against when raising purchase orders. Often the result is the user selecting the wrong contract.
Have you any suggestions on why this error message is appearing?
Many Thanks,
Sarah

1465740 - SRM document is stuck in the approval process
Symptom
Workflow hangs.
Workflow gets stuck.
SRM document in status waiting.
Approval process cannot continue.
SRM document frozen in status 'awaiting approval'.
BBP_PD 443 Document is still being processed in the background; Try again later
BBP_ICON_TEXTS 049 No workflow started. Application error occurred
Environment
SAP Supplier Relationship Management
Reproducing the Issue
Create or change a document in SRM.
Cause
*Not possible to identify root cause without further deeper analysis
Resolution
Find the object guid of your SRM document via transaction BBP_PD.
Then display the relevant workflow instance via transaction SWI6 using the following steps:
Select BOR object type.
Enter your object type.
Enter your guid (or document number in the case of shopping cart) in the Key field.
Select variant All Instances.
Select selection period All.
Hit execute.
Click on icon 'Display workflow log'.
Click on icon 'List with technical details'.
Click on icon 'Print Log'.
Record the date and time of the very last step in the workflow log.
Using the date and time of the last workflow step, here are some transactions that can be used to investigate the root cause of the problem.
SM58 - check for stuck remote function calls
ST22 - check for system dumps
SM13 - check for stuck update requests
SM21 - check in the system log for anything unusual
SWUD - run a consistency check on the workflow
Enter the task number and hit enter e.g. 14000044
Choose 'Test Environment' and flag 'Including parts'
Execute
Choose 'Consistency check for components' and flag 'Including subworkflows'
Execute
Red lights indicate an error in the definition.
Header Data
Released on 05.05.2010 09:53:08
Release status Released to Customer
Component SRM-EBP-WFL Workflow
Priority Normal
Category Problem

How can identify the default currency for a customer?

How can identify the default currency for a customer?
I know that this is being determined when you create a sales order for a particular customer, for example, so I could break this process open and find out what it uses. But I thought it worth asking in this forum first.
Blue

Hi Gary,
As per my understanding of your question I am replying , If you are looking some thing else then I request you to please elaborate your query.
If you see the BP sales area data in transaction BP, In billing tab you maintain the currency for a customer which is default currency when you create a sales order.
<b>Reward points if it helps!!</b>
Best regards,
Vikash

Recorded for outbound processing in SXMB_MONI???

Hi XI friends,
in my file to abap proxy,
in sxmb_moni i am getting message like "recorded for outbound processing" and Q status is stopped.
please help me.
thanks and regards
ram

Hi friends..
Trace is like this
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?> <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 = XIParty</Trace>
<Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>
<Trace level="1" type="T">Sender party external = </Trace>
<Trace level="1" type="T">Sender party normalized = </Trace>
<Trace level="1" type="T">Party normalization: receiver </Trace>
<Trace level="1" type="T">Receiver scheme external = </Trace>
<Trace level="1" type="T">Receiver agency external = </Trace>
<Trace level="1" type="T">Receiver party external = </Trace>
<Trace level="1" type="T">Receiver party normalized = </Trace>
<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST"></Trace>
<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.1</Trace>
<Trace level="2" type="T">Host = dcexi0605.aaaa.com:8030</Trace>
<Trace level="2" type="T">Server protocol = HTTP/1.1</Trace>
<Trace level="2" type="T">Remote address = 10.161.20.123</Trace>
<Trace level="1" type="T">COMMIT is done by XMB ! </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS"></Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE"></Trace>
<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>
<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 = BGX</Trace>
<Trace level="3" type="T">client = 100</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = XIAFUSERBGX</Trace>
<Trace level="1" type="Timestamp">2007-02-28T10:29:00Z 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>
<Trace level="1" type="T">Message-GUID = D5951F70C64311DBB7213A3BFF6537A2</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>
<Trace level="3" type="T">QOS = EO</Trace>
<Trace level="3" type="T">Message-GUID = D5951F70C64311DBB7213A3BFF6537A2</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 : XBTI0006</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTI0006</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 = D5951F70C64311DBB7213A3BFF6537A2</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>
<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>
<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 = BGX</Trace>
<Trace level="3" type="T">client = 100</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = XIAFUSERBGX</Trace>
<Trace level="1" type="Timestamp">2007-02-28T10:29:00Z CET </Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC"></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">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="3" type="T"> </Trace>
<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>
<Trace level="3" type="T"> </Trace>
<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>
<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>
<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>
<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>
<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>
<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>
<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>
<Trace level="3" type="T"> </Trace>
<Trace level="1" type="Timestamp">2007-02-28T10:29:00Z CET Begin of pipeline processing PLSRVID = CENTRAL</Trace>
<Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
<Trace level="1" type="Timestamp">2007-02-28T10:29:00Z 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>
<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>
<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">Classic Receiver Determination via Rules. </Trace>
<Trace level="2" type="T">Check conditions for rule line no. 1 </Trace>
<Trace level="2" type="T">...valid Receiver w/o Condition: - SAP_ERP_aaaa_PPR </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">2007-02-28T10:29:00Z 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">2007-02-28T10:29:00Z 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>
<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>
<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) SAP_ERP_aaaa_PPR MI_IN_S_StockAdj </Trace>
<Trace level="2" type="T">...valid InbIf without Condition: MI_IN_S_StockAdj </Trace>
<Trace level="2" type="T">Number of receiving Interfaces:1 </Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2007-02-28T10:29:00Z 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>
<Trace level="1" type="Timestamp">2007-02-28T10:29:00Z 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>
<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>
<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>
<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 = XBTOG___0002</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>
<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>
<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-RESTART_ERROR_MESSAGE"></Trace>
<Trace level="3" type="T">Trace object available again now. OK. </Trace>
<Trace level="3" type="T">manual Restart Flag X</Trace>
<Trace level="3" type="T">Message Guid D5951F70C64311DBB7213A3BFF6537A2</Trace>
<Trace level="3" type="T">Version 000</Trace>
<Trace level="3" type="T">Pipeline ID CENTRAL</Trace>
<Trace level="3" type="T">EOIO Force I</Trace>
<Trace level="3" type="T">Restart Trace </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="T">Error of the prevous version: </Trace>
<Trace level="3" type="T">Area </Trace>
<Trace level="3" type="T">Error ID </Trace>
<Trace level="3" type="T">Restart of Queue? </Trace>
<Trace level="1" type="T">Persisting message with status ManualRestart, version: 003</Trace>
<Trace level="1" type="T">*************************************** </Trace>
<Trace level="1" type="T">*   Setup of qRFC Scheduler OK!!! </Trace>
<Trace level="1" type="T">*************************************** </Trace>
<Trace level="3" type="T">Call qRFC .... MsgGuid = D5951F70C64311DBB7213A3BFF6537A2</Trace>
<Trace level="3" type="T">Call qRFC .... Pipeline = CENTRAL</Trace>
<Trace level="3" type="T">OK. </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST"></Trace>
<Trace level="3" type="T">Persisting message Status = 016</Trace>
<Trace level="3" type="T">Message version 005</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-RESTART_ERROR_MESSAGE"></Trace>
<Trace level="3" type="T">Trace object available again now. OK. </Trace>
<Trace level="3" type="T">manual Restart Flag X</Trace>
<Trace level="3" type="T">Message Guid D5951F70C64311DBB7213A3BFF6537A2</Trace>
<Trace level="3" type="T">Version 005</Trace>
<Trace level="3" type="T">Pipeline ID CENTRAL</Trace>
<Trace level="3" type="T">EOIO Force I</Trace>
<Trace level="3" type="T">Restart Trace </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="T">Error of the prevous version: </Trace>
<Trace level="3" type="T">Area </Trace>
<Trace level="3" type="T">Error ID </Trace>
<Trace level="3" type="T">Restart of Queue? </Trace>
<Trace level="1" type="T">Persisting message with status ManualRestart, version: 005</Trace>
<Trace level="1" type="T">*************************************** </Trace>
<Trace level="1" type="T">*   Setup of qRFC Scheduler OK!!! </Trace>
<Trace level="1" type="T">*************************************** </Trace>
<Trace level="3" type="T">Call qRFC .... MsgGuid = D5951F70C64311DBB7213A3BFF6537A2</Trace>
<Trace level="3" type="T">Call qRFC .... Pipeline = CENTRAL</Trace>
<Trace level="3" type="T">OK. </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST"></Trace>
<Trace level="3" type="T">Persisting message Status = 016</Trace>
<Trace level="3" type="T">Message version 006</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>
<Trace level="3" type="T">message version successfully read from persist version= 006</Trace>
<Trace level="2" type="T">Increment log sequence to 007</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 = BGX</Trace>
<Trace level="3" type="T">client = 100</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = saa_aaa</Trace>
<Trace level="1" type="Timestamp">2007-02-28T11:28:10Z CET </Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC"></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">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="3" type="T"> </Trace>
<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>
<Trace level="3" type="T"> </Trace>
<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>
<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>
<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>
<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>
<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>
<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>
<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>
<Trace level="3" type="T"> </Trace>
<Trace level="1" type="Timestamp">2007-02-28T11:28:10Z 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">2007-02-28T11:28:10Z 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>
<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>
<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 7344EE703ACE3FE5AB19EDA1D3F48BBC </Trace>
<Trace level="3" type="T">Version ID of Interface Mapping B2CF8EF067FF11DBA742D7830A967135 </Trace>
<Trace level="1" type="T">Interface Mapping http://aaaa.com/xi/PROCESS/PPE/ERP_MES IM_MES_StockAdj_TO_SAP </Trace>
<Trace level="3" type="T">Mapping Steps 1 JAVA com/sap/xi/tf/_MM_MES_StockAdj_To_SAP_ </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_MES_StockAdj_To_SAP_. </Trace>
<Trace level="2" type="T">Call method execute of the application Java mapping com.sap.xi.tf._MM_MES_StockAdj_To_SAP_ </Trace>
<Trace level="2" type="T">Java mapping com/sap/xi/tf/_MM_MES_StockAdj_To_SAP_ completed. (executeStep() of com.sap.xi.tf._MM_MES_StockAdj_To_SAP_ </Trace>
<Trace level="3" type="T">Dynamic configuration is empty </Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2007-02-28T11:28:10Z 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 = 007</Trace>
<Trace level="3" type="T">Message version 007</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="1" type="B" name="PLSRV_OUTBOUND_BINDING">
<Trace level="1" type="Timestamp">2007-02-28T11:28:10Z 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>
<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>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL"></Trace>
<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">-BS_FTP_MES_GeneralServices </Trace>
<Trace level="2" type="T">-SAP_ERP_aaaa_PPR </Trace>
<Trace level="2" type="T">http://aaaa.com/xi/PROCESS/PPE/ERP_MES.MI_IN_S_StockAdj </Trace>
<Trace level="2" type="T">Channel found: - SAP_ERP_aaaa_PPR - CC_IN_SAP_XI_StockAdj </Trace>
<Trace level="2" type="T">no header mapping defined </Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2007-02-28T11:28:10Z 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 = 008</Trace>
<Trace level="3" type="T">Message version 008</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="1" type="B" name="PLSRV_CALL_ADAPTER"></Trace>
<Trace level="1" type="Timestamp">2007-02-28T11:28:10Z CET Start of pipeline service processing PLSRVID= PLSRV_CALL_ADAPTER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV"></Trace>
<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>
<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>
<Trace level="3" type="T">Channel for Integration Engine: XI</Trace>
<Trace level="3" type="T"> </Trace>
<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 = IENGINE</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>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL"></Trace>
<Trace level="1" type="B" name="CL_XMS_PLSRV_IE_ADAPTER-ENTER_PLSRV">
<Trace level="3" type="T">Channel for Integration Engine: XI</Trace>
<Trace level="1" type="T">Sender: Header mapped to</Trace>
<Trace level="1" type="T">Party = </Trace>
<Trace level="1" type="T">Agency = </Trace>
<Trace level="1" type="T">Scheme = </Trace>
<Trace level="1" type="T">Service = BS_FTP_MES_GeneralServices</Trace>
<Trace level="1" type="T">Receiver: Header mapped to</Trace>
<Trace level="1" type="T">Party = </Trace>
<Trace level="1" type="T">Agency = </Trace>
<Trace level="1" type="T">Scheme = </Trace>
<Trace level="1" type="T">Service = SAP_ERP_aaaa_PPR</Trace>
<Trace level="1" type="T">Party denormalization: sender </Trace>
<Trace level="1" type="T">Sender target scheme = </Trace>
<Trace level="1" type="T">Sender target agency = </Trace>
<Trace level="1" type="T">Sender party normalized = </Trace>
<Trace level="1" type="T">Sender party external = </Trace>
<Trace level="1" type="T">Party denormalization: receiver </Trace>
<Trace level="1" type="T">Receiver target scheme = </Trace>
<Trace level="1" type="T">Receiver target agency = </Trace>
<Trace level="1" type="T">Receiver party normalized = </Trace>
<Trace level="1" type="T">Receiver party external = </Trace>
<Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP">
<Trace level="2" type="T">Addressing mode: url</Trace>
<Trace level="3" type="T">Host = dceaaaa08.aaaa.biz</Trace>
<Trace level="3" type="T">Port = 8010</Trace>
<Trace level="3" type="T">Transport protocol = HTTP      1.0</Trace>
<Trace level="3" type="T">Message protocol = </Trace>
<Trace level="3" type="T">Path = /sap/xi/engine?type=receiver</Trace>
<Trace level="2" type="T">Auth mode: basicSAP</Trace>
<Trace level="3" type="T">Conversion of language from char2 to char1 EN</Trace>
<Trace level="3" type="T">User = SAPJSF</Trace>
<Trace level="3" type="T">Client = 400</Trace>
<Trace level="3" type="T">Language = E</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 SAP </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="System_Error">HTTP-Client: exception during receive: HTTP_COMMUNICATION_FAILURE</Trace>
</Trace>
<Trace level="2" type="T">Switch back to normalized party (HTTP response)</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="T">Party normalization: receiver </Trace>
<Trace level="1" type="T">Receiver scheme external = </Trace>
<Trace level="1" type="T">Receiver agency external = </Trace>
<Trace level="1" type="T">Receiver party external = </Trace>
<Trace level="1" type="T">Receiver party normalized = </Trace>
<Trace level="2" type="T">Undo header mapping (HTTP response) </Trace>
<Trace level="1" type="T">Sender: Header before undo of mapping</Trace>
<Trace level="1" type="T">Party = </Trace>
<Trace level="1" type="T">Agency = </Trace>
<Trace level="1" type="T">Scheme = </Trace>
<Trace level="1" type="T">Service = BS_FTP_MES_GeneralServices</Trace>
<Trace level="1" type="T">Receiver: Header before undo of mapping</Trace>
<Trace level="1" type="T">Party = </Trace>
<Trace level="1" type="T">Agency = </Trace>
<Trace level="1" type="T">Scheme = </Trace>
<Trace level="1" type="T">Service = SAP_ERP_aaaa_PPR</Trace>
<Trace level="2" type="T">Sender: Header after undo of mapping</Trace>
<Trace level="2" type="T">Party = </Trace>
<Trace level="2" type="T">Agency = </Trace>
<Trace level="2" type="T">Scheme = </Trace>
<Trace level="2" type="T">Service = BS_FTP_MES_GeneralServices</Trace>
<Trace level="2" type="T">Receiver: Header before undo of mapping</Trace>
<Trace level="2" type="T">Party = </Trace>
<Trace level="2" type="T">Agency = </Trace>
<Trace level="2" type="T">Scheme = </Trace>
<Trace level="2" type="T">Service = SAP_ERP_aaaa_PPR</Trace>
</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 = 009</Trace>
<Trace level="3" type="T">Message version 009</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="3" type="System_Error">Error exception return from pipeline processing! </Trace>
<Trace level="1" type="T">Persist Message in Retry State </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST"></Trace>
<Trace level="3" type="T">Persisting message Status = 009</Trace>
<Trace level="3" type="T">Message version 010</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</SAP:Trace>
please guide me..
ram

While processing C015 - Getting Error 'Reservation 000005089 is already being Processed "

Hello,
I have created a customized Program script which will process MB1A , MIGO and CO15 simultaneously
MB1A - using BAPI
MIGO and CO15 using BADI
When i process for few records everything works fine. But when i process for 2000 records , after processing i am getting error at C015 "Reservation 000005089 is already being Processed".
I tried with wait time up to 8 seconds after MB1A , still i am getting same error.
Can any one suggest how to fix the issue.
BR,
Murali

Hi Murali,
do a wait loop before calling CO15 like:
locked = 'X'.
do.
    wait up to 5 seconds.
    CALL FUNCTION 'ENQUEUE_EMRKPF'
      EXPORTING RSNUM = your_rsnum
                 X_RSNUM = 'X'
      EXCEPTIONS FOREIGN_LOCK     = 2
                 SYSTEM_FAILURE   = 3.
    if sy-subrc                 EQ 0.
      clear                         locked.
      CALL FUNCTION 'DEQUEUE_EMMKPF'.
      exit.
    endif.
enddo.
Regards,
Klaus

Transaction is being processed by user - ITSM WebUI

I have integrated the Test Workbench with ITSM Incident Management. SMIN is customized to YMIN for this purpose.
Now I go to stwb_work and report a defect by clicking on "Create" under status. I am able to create a Message as usual.
Now I click on the message and open the same in WebUI, and try to edit it says "Transaction XXXXXXXX is being processed by user.
I tried closing the Test workbench transaction and still it says the same.
SM12 shows a lock entry for "CRMD_ORDERADM_H" and when I delete the entry, I am able to edit. Is there a way to release this lock after I have exited the message in the stwb_work -> Create Message area?
Also if I finally edit the transaction after some time on the WebUi and change the user status, this is not getting reflected in the test workbench "Message Overview"
Could you kindly let me know what could be a possible reason for this?

Hello Ranjih,
As per note 1821038 - Error "Transaction XXXXXXXXXX is being processed by user XXX" when try to edit message in CRM Web UI have you maintained his ?
For first case:
Please add the below entry which will put the document in "Display" mode after clicking "Save" Button.
Call transaction SM30.
Add an entry to table AGS_WORK_CUSTOM with NAME = 'IM_READONLY_AFTER_SAVE' and VALUE = 'X'.
BR,
K.

Custom Integrator Help

I have created a custom integrator using Desktop Integration Framework to load some data into a custom interface table that will be picked up and processed to base tables using an importer (plsql wrapper).
I have this all working, however I would like to be able to report errors back better. What I would like is a batch_id for the full spreadsheet, which I have managed easily using a sequence on the interface attribute called batch_id, this means all records will have that batch_id against them for this run of the interface. Next I need a unique id on each row passed in (record_id). To do this I was hoping to use a pre-import rule on the importer, i.e. pass in the batch_id from the interface_attribute to a plsql procedure that updates all records in the interface table just loaded that have the passed in batch_id with the record_id. The other method I thought was to use a pre-import rule of type SEQUENCE.
None of these I can get to work for the following reasons.
1. For a sequence pre-import rule, I cannot see how this gets associated with an interface attribute?
2. For the PLSQL procedure pre-import rule, I am unable to pass in the value of BATCH_ID which is already stored in an interface_attribute?
Any help on these, or another suggested method of doing this would be greatly appreciated.
Many thanks
Rob

Hi Nandhakumar.P,
thanks for your response. Please find the answers below:
- Set up a new custom function (similar to seeded function HR Integrator Setup).
System Administrator -> Application -> Function. Query back the seeded User Function Name = "HR Integrator Setup", make a note of the details, then add a custom function entitled "NTC_HR_LETTERS" with the same details.
- Add the custom function and other functions to Desktop Integration responsibility.
System Administrator -> Application -> Menu. Query back User Menu Name = "Desktop Integration Menu" and add the following functions:
WITHOUT PROMPT
a. HR Integrator Setup
b. HR Maintain Integrator Form Functions
c. HR Disable Integrator
d. HR ADI Document Overwrite Page
e. HR ADI Document Upload Page
f. The custom function created in previous step ("NTC_HR_LETTERS")
WITH PROMPT
g. HR ADI Document Management Page
- Add the relevant functions to end user's responsibility menu.
System Administrator -> Application -> Menu. Query back menu attached to custom responsibility of end user that will perform the action once set up.
Add the following:
a. The custom function "NTC_HR_LETTERS" as created previously (without prompt)
b. Desktop Integration - Create Document (With Prompt. This function will be used to generate letters)
- Add new category "other" to HR_ADI_DOCUMENT_TYPE lookup.
SA_Application Developer -> Application -> Lookups -> Common. Query back Type = HR_ADI_DOCUMENT_TYPE and add a new entry entitled "Other". This document type is later assigned to the Word document I upload and link to the integrator.
I hopoe that answers your questions.
Regards,
Hazel

Message: Person is already being processed by user &3 &4

Hi,
The message " Person is already being processed by user &3 &4" is appearing when the approver is trying to approve leave of an employee.
Please help.

It means that the user HR record is locked for editing by another person or that the payroll lock is on.
have a look in SM12 to see if the personnel number is in one of the locks.

Inbound ECC, ADRMAS/DEBMAS Processing with Customer # Assignment

I am looking for someone with recommendations on how we can get ADRMAS and DEBMAS IDocs transformed with new customer number and processed in proper order in ECC. The IDocs are being sent from a hub MDG system with a hub customer number in them. They get sent over via ALE to the destination ECC system and we have them set to not process immediate. We plan to process them via a program that needs to look up the next available customer number on the ECC (using internal number assignment) and process both IDocs with the new ECC customer number.
We need to coordinate the ADRMAS processing before its' respective DEBMAS.
Any suggestions are appreciated.
Thank you,
Keith

Hi Keith,
You might want to consider using "Serialization by Message Type" in the receiving system.
Please refer to below link which has more information :
Serialization of Messages - ABAP Development - SCN Wiki
Also, if you have internal number assignment for the customer, the system will propose a new available customer number.
Thanks,
Kumaran

Oracle IIS number of processes grows to big

I am supporting a bad, packaged ASP program that runs under IIS.
IIS 4
NT 4
Oracle 8.1.6.0
After a few hours the number of sessions is about 25, which is ok, but the number of processes exceeds the limit (240).
We are investigating how this can be, but in the meantime I would like to automatically kill processes that are waiting, or belong to inactive sessions.
(By the way, is there a way to timeout sessions? or processes?)
My next task here is to see if any of them are locked, but I don't think so -- I think the web application is leaving them as orphans.
Thanks.
John Frame
[email protected]

A bit more news. Basically the problem is identified by the fact that there are about 150 records in V$PROCESS that do not match to anything in V$SESSION.
I will reply when there is news about what is causing this.
You are right about MTS, if it is used in an IIS/ASP environment it will reduce the Oracle memory usage to about 4% of previous numbers. Amazing, MTS has connection pooling for cheap asp pages! (set it to multi, not dedicated).
[email protected]

Sales document 400136021 is currently being processed (by user MNAUSHAD (C2

Hi Friends,
   Iam using Mobile Sales and iam getting an error when iam opening the sale order created in laptops
   Scenario : Sale order created in laptop got replicated in CRM and R/3 and delivery got created in
                   R/3.
                   The replicated sales document is not seen in the Document flow in CRM enterprise
                    I could not find any queue's in SMQ2 or in SMQ1 both in R/3 or in CRM.
                    when i open the same sale order in VA02 iam getting the error.
   Sales document 400136021 is currently being processed (by user MNAUSHAD (C2)
   Let me know if any of you has faced the same issue,
   Regards,
   Satish Kumar

Hi Wolfard,
Please find my answers,
1. Does this error also occur when creating a similar sales document in CRM directly (i.e. it is rather a   CRM related issue than mobile related)? - No from CRM enterprise to R/3 i dont find an error- It is more of a Sync issue between Mobile> CRM> R/3.
b) Do you know a user or batch name in CRM resp R/3 with that name mentioned by you?
    I know the user name - but this user name is not at all related.
c) Please be aware that those queues smq1/2 are dynamical i.e. after processing the data the entries were deleted again; only in case of a sys fail the queues would be stopped; in the particular case of waiting for processing in R/3 there would be a queue status "WAITUPDA"
I accept the queues are dynamic and it will deleted after it is processed,, The issue is that i dont find any queue in SMQ1 in R/3 and also in SLG1 on that particular date i could find the Log number with the error
With the help of Log error i can find out the sale order.
Trust it is ok
satish

Sales Order is being processed

Hi All,
1) My scenario is sales bom, the header is delivered and the line items are billed, after completion of billing the sales order status for header is complete and the line items status is being process...due to this these sales orders are showing as open sales orders,
2) I want to know a sales process for an asset...at the time of purchase there is no excise has been paid, so it means we canu2019t avail the excise at the time sale also... So at the time of sale the cenvat entries will not be there..Kindly give your valuable suggestions...whether the asset should sold without excise...whereas the configuration is with formula based pricing......
Thanks & Regards,
Mani

Hi Pete,
Thank you so much for your reply.
At that point of time, sales order is not in open condition. Actually that return order will be created from service notification through action box items - workflow. Also the sales order no xxxxxx is the return order number & its not the original sales order number.
Regards,
Maheswaran.

Delivery Document has been created - showing the status of Being Processed.

Hi All.
I am facing the following typical problem.
1. Sales order has been created - showing the status of COMPLETED.
2. Delivery Document has been created - showing the status of Being Processed.
3. Goods Issue document created successfully- showing status as COMPLETE
4. Billing Document has created successfully - showing the status as COMPLETED.
5. Customer Account got updated properly.
Query: Despite of completion of SO, DELIVERY, GOODS ISSUED, AND BILLING DOCUMENT u2013 and accounting document is cleared why the outbound Delivery document status is showing as BEING PROCESSED.
If I go T-code Vlo3n see document flow
Delivery 5080789885 being processed.
Go to VF03 document flow also it is showing
Delivery 5080789885 being processed.
Aditya

Hi ALL,
Further to my query I would like to clarify the following:
It is happening since 2004 all Bom components status (Delivery being processed) all the BOM main items header status is showing completed.
It not impacting the business, but suddenly user raise query SO, DELIVERY, GOODS ISSUED, AND BILLING DOCUMENT completed why still delivery showing as being processed.
1. I have checked at SO level -- all the line items were delivered. ie: delivery, goods issue, billing completed.
2. I checked the Header Level data completed and Item Level data being processed.
3. If I look into the each item level also it is showing as being processed.
4. Even the SALES ORDER HEADER LEVEL showing the status of Completed.
5. Removed credit check in delivery.
The only issue is OUTBOUND DELIVERY DOCUMENT: Status alone it is showing as ' Being Processed' -- surprisingly!
Aditya.

Identify record number being processed in Custom Integrator?

Similar Messages

Maybe you are looking for