Table growth for Async process
Hello,
Using SOA/BPEL 11g
Have deployed Async Bpel process and want to know (since this is async -- it must be saving or persisting state in some database tables ) what are the database table names THAT Async BPEL might be storing/persisting the STATE (for future use). Also, does anyone have the stats for "Table Growth" (MB) per xx number of request for BPEL process ?
thx
pp
Below are the table names were data is stored:
AUDIT_DETAILS
AUDIT_TRAIL
COMPOSITE_INSTANCE
COMPOSITE_INSTANCE_ASSOC
COMPOSITE_INSTANCE_FAULT
CUBE_INSTANCE
CUBE_SCOPE
DLV_MESSAGE
DLV_SUBSCRIPTION
DOCUMENT_CI_REF
DOCUMENT_DLV_MSG_REF
HEADERS_PROPERTIES
INSTANCE_PAYLOAD
REFERENCE_INSTANCE
REJECTED_MESSAGE
REJECTED_MSG_NATIVE_PAYLOAD
WFTASK
WI_FAULT
WORK_ITEM
XML_DOCUMENT
XML_DOCUMENT_REF
There are no fixed guidelines for the database growth. Database utilization is different for each process depending upon the payload sizes.
Similar Messages
-
Need table information for Business process ID and Business process status
Hi Guys/Sap,
I need PI table for business process ID(BPM) and Business process status table .Kind if any one know help me out .
I have checked blog but ia could only fine basic tables .
https://wiki.sdn.sap.com/wiki/display/XI/Useful%20ABAP%20tables%20in%20SAP%20XI.
Regards,
SriramHi Sriram,
Search SE11 for SWF* tables.
Regards,
Ravi -
Table for Output Processing log
Hi,
Can anyone tell me the table for Output processing Log.
I need to take this info for some interface issue.
MuthuHello,
Check out the table "CMFP" for output processing log.
Regards,
SARTHAK -
Stateful message processing for async scenario
Dear all,
my async scenarios:
1. RFC -> PI -> File
2. File -> PI -> RFC
Following facts:
- The second message is a response to the first one. Both message are separted and async.
- Scenario 2 can be send some hours after Scenario1.
- A response should only be send if a specified field in the message of first scenario is filled.
For example: Message in scenario has a field <ResponseNeeded>YES</ResponseNeeded>
This field does only exist in message of scenario 1.
- Both message have an ID field (e.g. <ID>4711</ID>) which can be used to identified the
corresponding message.
Questions:
- Is it possible to use stateful message processing for this scenario? Or do I need BMP + Correlation?
- A service interface with pattern "stateful" can only be used synchronously. So is it
possible to use this stateful for async message processing at least?
I would assume that I will need a BPM that sends the messsage and keep alive until a
response will be sends with same ID. After this I would check message of scenario1 and
send (or even not) the message of scenario2 to receiver depending on <ResponseNeeded>.
Thanks in advanced.
ChrisHi Chris,
Although BPM is possible here, I would not recommend you to use one here for the reason,
>>Scenario 2 can be send some hours after Scenario1.
This means you are keeping a process alive for so long which is not a good thing to do.
You could end up with a lot of open/live process instances.
Having said that, if you still wish to go ahead with BPM, the steps would be
1. Receive async (RFC req) - start process, correlation based on ID.
2. Switch step (Evaluate ResponseNeeded)
branch 1(True): a. Send asynch step - File
b. Receive async - File correlation - ID.
c. Send async - RFC call.
branch 2(false) a. Send async -File
3. Stop process.
Regards
Jai -
Table/Structure for process order's auto batch determined component.
Hi PP Gurus,
We're struggling to get the Structure/Table name where data pertaining to process order component which is batch managed and automatically batch determined goes. We know RESB is the table where it gets updated after saving Process order. But we want the structure/table name before saving the Released Process order. Can anybody please help to get it?
Thanks,
Abu ArbabAbuarab,
I think it will in structure CAUFVD. Following are the enchancements available as of ECC 6.0,
PPCO0001 Application development: PP orders
PPCO0002 Check exit for setting delete mark / deletion indicator
PPCO0003 Check exit for order changes from sales order
PPCO0004 Sort and processing exit: Mass processing orders
PPCO0005 Storage location/backflushing when order is created
PPCO0006 Enhancement to specify defaults for fields in order hea
PPCO0007 Exit when saving production order
PPCO0008 Enhancement in the adding and changing of components
PPCO0009 Enhancement in goods movements for prod. process order
PPCO0010 Enhancement in make-to-order production - Unit of measu
PPCO0012 Production Order: Display/Change Order Header Data
PPCO0013 Change priorities of selection crit. for batch determin
PPCO0014 Select process orders for external relationships
PPCO0015 Additional check for document links from BOMs
PPCO0016 Additional check for document links from master data
PPCO0017 Additional check for online processing of document link
PPCO0018 Check for changes to production order header
PPCO0019 Checks for changes to order operations
PPCO0020 Process order: Display/change order header data
PPCO0021 Release Control for Automatic Batch Determination
PPCO0022 Determination of Production Memo
PPCO0023 Checks Changes to Order Components
Regards,
Prasobh -
DAC Metadata Table information for Change Capture process
Hi All,
is there any separate metadata tables available for the Change Capture process configured in DAC for siebel , separately , like w_etl_step_run ?
I just wonder that the information is not available elsewhere
Please help with your ans.
- M.This forum is for OLAP option of Oracle database.
Post your DAC question in BI-Apps forum at:
Business Intelligence Applications
. -
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
ramHi friends..
Trace is like this
<?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 = 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 -
Information Text for multiple process.
Hi All,
I have a page with multiple process.
Process 1. Upload multiple files to table using Process Row
Process 2. The Files are rearranged to another table, ready for analysis.
Process 3. Uploaded file is analysed for errors 1,
Process 4. Analyse for Error 2.
The problem is when the upload file size growth with more number of uploads. It take quite a longer time to upload and then analyse.
Is there a way i can pass back a value to the Page and display what process has been done and what process is running currently.
or Any ideas ?
Thanks in Advance
BalaHi,
You can create background process
See if this help you
http://download.oracle.com/docs/cd/E14373_01/appdev.32/e11838/advnc.htm#BABGHIFB
Br, Jari -
COm_SE_CPOINTER Table growth
Dear all
In our Trex Server we are using two business objects are indexed (Abap Objects) Currently our COM_SE_CPOINTER table growth is 55 GB. For the both object we have schedule back ground job to delete the data older than one month, in the Com_se_cpointer table has lots of other objects are there weather we can delete those object by using the com_se_cpointer_delete program? If we are doing that it will have any other impact? But our usage is only the two objects other then we are not using anything.
Kindly guide us
Regards
SriramPlease see OSS 1317755:
For performance reasons, you must ensure that the change pointer tables
COM_SE_CPOINTER and COM_SE_CPOINTER2 do not become too large. Therefore,
immediately after the SES indexes are backed up, we recommend that you delete
the change pointers that have been processed up to that time. To do this, call
transaction SES_ADMIN and choose "Utilities -> Delete Change Pointers".
Alternatively, you can call the program COM_SE_CPOINTER_DELETE directly.
Best regatrds,
Kai -
The request could not be submitted for background processing.
Post Author: Chriss
CA Forum: Administration
It's an BOE XI SR2, on Win2k3 server, with a print cluster with two print spools, handling 3000+ printers. I discovered this error to be intermittent and only on one of the spools. It turned out that the only common factor was an HP4250 print driver. I backed all the 4250s down to 4200 drivers and the intermitent error ("Error in File. The request could not be submitted for background processing.") went from about 100 a day to zero. The other spool had a different version of the HP4250 driver and would on rare occassion cause this error, "Error in File ... Page header or footer longer than a page." but never the background processing error.
For reference, when I got this error in XI R1, this was the solution for 'the error with one name and many causes':The error "The request could not be submitted for background processing" can be related to a corrupt or wrong versioned crpe32.dll in the Crystal bin folder. Renaming to crpe32.dll_bak and using the repair command in the the "Add/Remove Programs" tool in the "Control Panel" will reinstall the correct dll. Then restart the Crystal services.Post Author: krishna.moorthi
CA Forum: Administration
For Crystal reports :
Error : "The request could not be submitted for background processing"
I think,this was not related to a corrupt or wrong versioned crpe32.dll.
but the below mentioned is one of the reason for getting this error.
I got the error when the main report(crystalreports10) having more than 2 subreports not assigned proper tables for the subreports.
Example: (this code raise the abone mentioned error.)
rpt.SetDataSource(Exdataset);
rpt.Subreports["subreportname1"].SetDataSource(Exdataset); // Exdatatset.Tables[1]
rpt.Subreports["subreportname2"].SetDataSource(Exdataset);// Exdatatset.Tables[2] -
How to get the List of Database Objects (Table/View) for a given APEX Page.
Hi,
I have an application and that consist of pages like page1,2,3,.....
*1.* I want a report which can give me the list of all the Pages1,2,3,....
I am using the following query to acheive this.... THIS IS FINE..
select a.workspace, a.owner, a.application_name, b.page_id, b.page_name
from apex_applications a,
apex_application_pages b
where a.workspace = b.workspace
and a.application_id = b.application_id*2. Now, I want for each individual page*, the list all the database objects (tables/views), which that page is using.
I am using ALL_DEPENDENCIES , but I am not getting the result.
So, want to know if there any view/table, where I can get the Application Pages & there database object list...
Thanks,
DeepakHari,
Thanks for the response.
The view APEX_APPLICATION_PAGE_DB_ITEMS will only give me the table name related to any Page Items defined to that page..It will not give me all the database objects..
suppose we have a Page, having a report based on multiple tables and there is no Page items defined on that page, we will not have any value in this ....DB_ITEMS table. same thing if we have define some PL|SQL(using some table/view) in a Process, that will not be populated in .....DB_ITEMS table. I want some thing like all the database objects (table/views/function/procedure/.....) for a particular Page ID.
Thanks,
Deepak -
Hi,
We have gone line with SAP ECC for retail scenario recently. Our database is growing 3 GB per day which includes both data and index growth.
Modules configured:
SD (Retail), MM, HR and FI/CO.
COPA is configured for reporting purpose to find article wise sales details per day and COPA summarization has not been done.
Total sales order created per day on an average: 4000
Total line items of sales order on an average per day: 25000
Total purchase order created per day on an avearage: 1000
Please suggest whether database growth of 3 GB per day is normal for our scenario or should we do something to restrict the database growth.
Fastest Growing tables are,
CE11000 Operating Concern fo
CE31000 Operating Concern fo
ACCTIT Compressed Data from FI/CO Document
BSIS Accounting: Secondary Index for G/L Accounts
GLPCA EC-PCA: Actual Line Items
FAGLFLEXA General Ledger: Actual Line Items
VBFA Sales Document Flow
RFBLG Cluster for accounting document
FAGL_SPLINFO Splittling Information of Open Items
S120 Sales as per receipts
MSEG Document Segment: Article
VBRP Billing Document: Item Data
ACCTCR Compressed Data from FI/CO Document - Currencies
CE41000_ACCT Operating Concern fo
S033 Statistics: Movements for Current Stock (Individual Records)
EDIDS Status Record (IDoc)
CKMI1 Index for Accounting Documents for Article
LIPS SD document: Delivery: Item data
VBOX SD Document: Billing Document: Rebate Index
VBPA Sales Document: Partner
BSAS Accounting: Secondary Index for G/L Accounts (Cleared Items)
BKPF Accounting Document Header
FAGL_SPLINFO_VAL Splitting Information of Open Item Values
VBAP Sales Document: Item Data
KOCLU Cluster for conditions in purchasing and sales
COEP CO Object: Line Items (by Period)
S003 SIS: SalesOrg/DistCh/Division/District/Customer/Product
S124 Customer / article
SRRELROLES Object Relationship Service: Roles
S001 SIS: Customer Statistics
Is there anyway we can reduce the datagrowth without affecting the functionalities configured?
Is COPA summarization configuration will help reducing the size of the FI/CO tables growth?
Regards,
Nalla.user480060 wrote:
Dear all,
Oracle 9.2 on AIX 5.3
In one of our database, one table has a very fast growth rate.
How can I check if the table growth is normal or not.
Please advice
The question is, what is a "very fast growth rate"?
What are the DDL of the table resp. the data types that the table uses?
One potential issue could be the way the table is populated: If you constantly insert into the table using a direct-path insert (APPEND hint) and subsequently delete rows then your table will grow faster than required because the deleted rows won't be reused by the direct-path insert because it always writes above the current high-water mark of your table.
May be you want to check your application for such an case if you think that the table grows faster than the actual amount of data it contains.
You could use the ANALYZE command to get information about empty blocks and average free space in the blocks or use the procedures provided by DBMS_SPACE package to find out more about the current usage of your segment.
Regards,
Randolf
Oracle related stuff blog:
http://oracle-randolf.blogspot.com/
SQLTools++ for Oracle (Open source Oracle GUI for Windows):
http://www.sqltools-plusplus.org:7676/
http://sourceforge.net/projects/sqlt-pp/ -
Error in PB60 "Settings for word processing system are wrong"
Hello Everybody
I am working on recruitment,
i have create applicant activity in SPRO, but when i was going to create applicant activity PB60 maintain and entering the personal number the error display " "Settings for word processing system are wrong"
then i check feature set word processing system.
plz anybody guide me how to resolved this problem
thanks
urvashiHi Urvashi,
Please check the following in your system:
- Go to PE03
- feature 'WPROC'
- select 'Attributes'
- press 'Display'
- press 'Struct.'
- there you will find the Basic information 'Passing type'
This must be set to '2' (Table Transfer). If this is set
to '1' i.e. please change this entry.
Hope this help
Sarah -
Table name for the status Cstd
Hi
Need the table name for the sales order line item status Cstd
Steps
Go to the sales order line item
go to the Tab status
under that in processing status--> system status
here Cstd is there but we are not able to find the table name for that
Strecture is RV45A and field name is STTXT
we are planing to restrict the PP order being released if the status is not Cstd
PP order should release if the status in Sales order line item is Cstd
Can you help to findout the table name foth above field
Thanks
Kameshwar RaoHi
Table name is VBUP and the method to check the creation of Production order is BADI workorder_update
I would rather prefer to have a COSTED status as a part of the incompletion Log in SD module so that you cant save a SO if SO is not costed... See if that is possible for you
OR you can also change your Req Class settings to auto calculate SO cost estimate upon Saving SO
br, Ajay M -
Error Handling in table control for line item.
Hi,
Please how to do error handling in table control for line item in bdc,i have used format_message for header but i don't no fill decamps internal tabled and how to do background processing in call transaction.
ThanksBackground processing is not possible using call transaction method.
You can create an executable program which can have CALL TRANSACTION BDC code. And this can be run in background.
What do you exactly mean by Error handling for Items in table control. Can you give some more details.
Maybe you are looking for
-
Converting image data to given ICC Profile?
I am considering using a pro printer to print my photos. On their site they provide ICC profiles for there printer which I can use to soft proof. The site states "Our Fuji 570 printer does not read embedded profiles, so the image data must be convert
-
Remove password for development mode
Is there a way to be in development mode and not have password set up? Z10 is my primary phone, and it annoys me that I MUST have password on whenever I am in development mode. Can I be in dev mode without a password? It would make my life a bit easi
-
Hello, I cannot find a code anywhere that works for user defaults in xcode. I tried: http://macscripter.net/viewtopic.php?id=24666 http://macscripter.net/viewtopic.php?id=16298 but I cannot seem to get it to work. The build keeps failing on me. Does
-
When i open safari then all tabs of previous session are loading. its not awful?
Hi, when i open safari then all tabs of previous session are loading. we want just load the tab what i have click. please add this beutiful option in the next release. we use safari coz we know its the best. nomanrahid.
-
Error 10845 in VI Logger with NI 4350
I have just installed VI Logger 2.0 full version for use with my NI 4350 USB box. I get an error in a simple analog read of 10845, Data could not be read from my devvice fast enough. Is there a wy to slow down the sampling or speed up the bus speed?