B1SO2B1PO scenario is not working

Hi
I've create BizPackage B12B1_IC_PUR.
When I 've create 2 BIU
1. BIU B1PO2B1SO to B12B1_IC_PUR BizPacgae for BizSteps Snd->Rcv
2. BIU B1SO2B1PO to B12B1_IC_PUR BizPacgae for BizSteps Rcv->Snd
Then I've got yellow color BizPackage box with "BIU.B1SO2B1PO is not registered to B1 Event Dispatcher" error info.
I've checked BizPackageMeta.xml
<BizStepList>
          <BizStep Name="Z.EVO.B1PO2B1SO" Id="biu.Z.EVO.B1PO2B1SO" isMandatory="yes" Direction="1" RegisterED="yes"/>
          <BizStep Name="Z.EVO.B1SO2B1PO" Id="biu.Z.EVO.B1SO2B1PO" isMandatory="yes" Direction="-1" RegisterED="no"/>
     </BizStepList>
This "BIU.B1SO2B1PO is not registered to B1 Event Dispatcher" error info was gone after I've manually changed RegisterED="no" to RegisterED="yes".
B1PO2B1SO BIU is working OK but B1SO2PO BIU is not working.
I can't find any message details for B1SO2PO.
I've got only Subsidiary company as Sender system name from Monitoring->message log details.
Event filter was setting with "1,2,17,22" for Headquarter company.
I hope someone can help me.
Thanks
Joanne

Hi,
I've found one thing you should know about this issue.
BIU B1SO2B1PO is working when I updated exsting Sales order.
Task filter is "N" on bumeta documetation
Why this BIU does not create any message when sales order is added.
This is a modified details on B1SO2B1PO BIU.
          <xsl:variable name="DocRefNo" select="BOM/BO/Documents/row/NumAtCard"/>
          <xsl:choose>
               <xsl:when test="string-length($DocRefNo) != 0">
                    <BOM xmlns="">
                         <BO>
                              <AdmInfo>
                                   <Object>22</Object>
                                   <Version>2</Version>
                              </AdmInfo>
                              <QueryParams>
                                   <DocEntry>
                                        <xsl:value-of select="BOM/BO/Documents/row/NumAtCard"/>
                                   </DocEntry>
                              </QueryParams>
                              <Documents>
                                   <row>
                                        <NumAtCard>
                                             <xsl:value-of select="BOM/BO/Documents/row/DocEntry"/>
                                        </NumAtCard>
                                   </row>
                              </Documents>
                         </BO>
                    </BOM>
               </xsl:when>
               <xsl:otherwise>
                    <b1im_skip xmlns=""/>
               </xsl:otherwise>
          </xsl:choose>

Similar Messages

Import scenario package not working

Hi exports,
On a test environment i created a scenario which i now would like to transfer to another server.
I exported the correct scenario, but on the other server, the import is not working.
I can submit my package, it shows that there is no current version of this package, but hitting the "IMPORT" button doesnt do anything.
Im using (on both servers) SAP B1 9.0 pl 08 with the same integration framework.
Any idea's on how to solve this?
Kind regards
Frederik

Hi Radosla,
Yep, thx for the hint.
Looks like i put it on th test server in compatibility mode, but not on the real server.
Changing this with F12 to IE 8 did the trick!
Regards
Frederik

Scenario Manager not working in ATG

Hi,
I have a problem with scenario manager. I have a scenario manager which triggers order confirmation mails. When the jboss server starts it throws the below error.
Unable to declare this instance as the default ProcessEditorServer. Another instance, Dev-254:8850, has already been run against this schema, and has declared itself as the default ProcessEditorServer. This instance will be started as an individual server. To declare this instance as the ProcessEditorServer, either configure the /atg/scenario/scenarioManager.xml file, or remove the row from dss_server_id whose server_id column is Dev-245:8850. The first option is the recommended one, since it will prohibit this problem from occurring in the future.+
But for systems, it is working fine. some others it is not working.
Any idea?

I guess you are using a Common Schema for all developers. Whenever a first server is starting, it will register itself as the Process Editor Server, this must be one of the developer machine and he will be able to create/edit scenario in his machine but for others its not.
One thing you can try out is that (not sure it works or not), configure localhost:8850 (drp_port) using /atg/scenario/scenarioManager.xml; it might help all the developers to use Scenario editor. As per ATG you should use one dedicated instance for process editor server, you may try out the localhost way for dev purpose, do let me know if it works for you.
/DSS/config/config.jar has the OOB scenarioManager.xml file, sample configuration below.
+<process-manager-configuration>+
+<process-editor-server>+
+<server-name>localhost:8850</server-name>+
+</process-editor-server>+
+</process-manager-configuration>+
Cheers
R
Edited by: Rajeev_R on Mar 5, 2013 11:04 PM

Jdbc to rfc to jdbc scenario is not working

Hi...
We have done the JDBC to RFC to JDBC scenario using BPM, it was working fine in the last month. now we started testing the same scenario, that is not working. In SXMB_MONI it is showing only sender data is successful, it is not showing any RFC Receiver data & Jdbc Receiver data. in the CCM also Jdbc Sender CC is showing successfull and it is showing the successful messages also, but in RFC Receiver CC
& JDBC Receiver CC it is not showing any thing.
please help on this...
Regards,
Pasi.

Hi
Check u r RFC response (put external break point)
and check wether it has data
rgds
srini

SOAP-XI-ABAP Proxy scenario suddenly not working... with some error.

Hi,
My interface is WS-XI-ABAPproxy.
It was working fine. And I was able to test end-to-end using XML spy.
After 5 days when I tested it again it is not working.
I didnt make any changes.
Today when I run, it is giving error in XI box.
Please find trace from XI box.
<?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="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
- 
<Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>
<Trace level="2" type="T">Request Line = POST /sap/xi/engine?type=entry HTTP/1.1</Trace>
<Trace level="2" type="T">Host = sapxidev.sw.schwans.net:8080</Trace>
<Trace level="2" type="T">Server protocol = HTTP/1.1</Trace>
<Trace level="2" type="T">Remote address = 10.1.5.143</Trace>
<Trace level="1" type="T">COMMIT is done by XMB !</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
- 
<Trace level="3" type="T">XMB was called with external pipeline PID = ENTRY</Trace>
<Trace level="3" type="T">Getting type of XMB...</Trace>
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="2" type="T">XMB kind = CENTRAL</Trace>
<Trace level="3" type="T">Start pipeline found</Trace>
<Trace level="2" type="T">Switch to external start pipeline PID = CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV">
<Trace level="3" type="T">No triggers found. OK.</Trace>
</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">XMB entry processing</Trace>
<Trace level="3" type="T">system-ID = XI1</Trace>
<Trace level="3" type="T">client = 100</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = XIAFUSR_XI1</Trace>
<Trace level="1" type="Timestamp">2007-12-27T23:10:34Z CET</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- 
<Trace level="1" type="T">Message-GUID = ED93DCC0B4D011DCCE59001438BE3377</Trace>
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- 
<Trace level="3" type="T">QOS = EO</Trace>
<Trace level="3" type="T">Message-GUID = ED93DCC0B4D011DCCE59001438BE3377</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 : XBTI0008</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTI0008</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 = ED93DCC0B4D011DCCE59001438BE3377</Trace>
<Trace level="3" type="T">Call qRFC .... Version = 000</Trace>
<Trace level="3" type="T">Call qRFC .... Pipeline = CENTRAL</Trace>
<Trace level="3" type="T">OK.</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="3" type="T">Version number = 000</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="3" type="T">Persisting message Status = 001</Trace>
<Trace level="3" type="T">Message version 000</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
- <Trace level="1" type="B" name="interface activity determination">
<Trace level="1" type="T">Version 000</Trace>
<Trace level="1" type="T">Message status 000</Trace>
<Trace level="1" type="T">Interface action INIT</Trace>
<Trace level="1" type="T">(must be INIT for a new determination)</Trace>
<Trace level="1" type="T">start CHECK_INTERFACE</Trace>
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface SqlSender_MI*</Trace>
<Trace level="1" type="T">select interface namespace http://tsfco:I_CRM_SQL_COM_SC:XX:BpFromSqlToCrm</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">end CHECK_INTERFACE</Trace>
<Trace level="1" type="T">Set interface action INIT into *MAST*</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
<Trace level="3" type="T">Trace object available again now. OK.</Trace>
<Trace level="3" type="T">Message was read from persist layer. OK.</Trace>
<Trace level="3" type="T">Message properties in XMB object were setup. OK.</Trace>
<Trace level="3" type="ToDo">Make sure we catch exceptions in persist read</Trace>
<Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
</Trace>
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="3" type="T">message version successfully read from persist version= 000</Trace>
<Trace level="2" type="T">Increment log sequence to 001</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="3" type="T">system-ID = XI1</Trace>
<Trace level="3" type="T">client = 100</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = XIAFUSR_XI1</Trace>
<Trace level="1" type="Timestamp">2007-12-27T23:10:34Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
<Trace level="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline attributes</Trace>
<Trace level="3" type="T">PID = SAP_CENTRAL</Trace>
<Trace level="3" type="T">ENABLE = 1</Trace>
<Trace level="3" type="T">TRACELEVEL = 0</Trace>
<Trace level="3" type="T">EXEMODE = A</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline elements</Trace>
<Trace level="3" type="T">ELEMPOS = 0001</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0002</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0003</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0004</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0007</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0008</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0009</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_RESPONSE</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="1" type="Timestamp">2007-12-27T23:10:34Z CET Begin of pipeline processing PLSRVID = CENTRAL</Trace>
- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
<Trace level="1" type="Timestamp">2007-12-27T23:10:34Z CET Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_RD_PLSRV</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">Start without given receiver</Trace>
<Trace level="2" type="T">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: - Sys_CR1_120</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-12-27T23:10:34Z 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 level="1" type="B" name="interface activity determination">
<Trace level="1" type="T">Version 001</Trace>
<Trace level="1" type="T">Message status 001</Trace>
<Trace level="1" type="T">Interface action INIT</Trace>
<Trace level="1" type="T">(must be INIT for a new determination)</Trace>
<Trace level="1" type="T">start CHECK_INTERFACE</Trace>
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface SqlSender_MI*</Trace>
<Trace level="1" type="T">select interface namespace http://tsfco:I_CRM_SQL_COM_SC:XX:BpFromSqlToCrm</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--start receiver interface action determination</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface *</Trace>
<Trace level="1" type="T">select interface namespace</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
<Trace level="1" type="T">end CHECK_INTERFACE</Trace>
<Trace level="1" type="T">Set interface action DEL into *MAST*</Trace>
</Trace>
</Trace>
- <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
<Trace level="1" type="Timestamp">2007-12-27T23:10:34Z CET Start of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_ID_PLSRV</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) Sys_CR1_120 CrmReceiver_MI</Trace>
<Trace level="2" type="T">...valid InbIf without Condition: CrmReceiver_MI</Trace>
<Trace level="2" type="T">Number of receiving Interfaces:1</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2007-12-27T23:10:34Z 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 level="1" type="B" name="interface activity determination">
<Trace level="1" type="T">Version 002</Trace>
<Trace level="1" type="T">Message status 001</Trace>
<Trace level="1" type="T">Interface action DEL</Trace>
<Trace level="1" type="T">(must be INIT for a new determination)</Trace>
<Trace level="1" type="T">Set interface action DEL into *MAST*</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" />
- 
<Trace level="1" type="Timestamp">2007-12-27T23:10:34Z CET Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_RECEIVER_SPLIT</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
<Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV" />
- 
<Trace level="3" type="T">Case handling for different plsrv_ids PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="2" type="T">got property produced by receiver determination</Trace>
<Trace level="1" type="T">number of receivers: 1</Trace>
<Trace level="1" type="T">Single-receiver split case</Trace>
<Trace level="1" type="T">Post-split internal queue name = XBTOI___0000</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Persisting single message for post-split handling</Trace>
<Trace level="1" type="T" />
<Trace level="1" type="T">Going to persist message + call qRFC now...</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="3" type="T">Persisting message Status = 012</Trace>
<Trace level="3" type="T">Message version 003</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
- <Trace level="1" type="B" name="interface activity determination">
<Trace level="1" type="T">Version 003</Trace>
<Trace level="1" type="T">Message status 001</Trace>
<Trace level="1" type="T">Interface action DEL</Trace>
<Trace level="1" type="T">(must be INIT for a new determination)</Trace>
<Trace level="1" type="T">Set interface action DEL into *MAST*</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
<Trace level="3" type="T">Trace object available again now. OK.</Trace>
<Trace level="3" type="T">Message was read from persist layer. OK.</Trace>
<Trace level="3" type="T">Message properties in XMB object were setup. OK.</Trace>
<Trace level="3" type="ToDo">Make sure we catch exceptions in persist read</Trace>
<Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
</Trace>
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="3" type="T">message version successfully read from persist version= 004</Trace>
<Trace level="2" type="T">Increment log sequence to 005</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="3" type="T">system-ID = XI1</Trace>
<Trace level="3" type="T">client = 100</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = XIAFUSR_XI1</Trace>
<Trace level="1" type="Timestamp">2007-12-27T23:25:53Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
<Trace level="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline attributes</Trace>
<Trace level="3" type="T">PID = SAP_CENTRAL</Trace>
<Trace level="3" type="T">ENABLE = 1</Trace>
<Trace level="3" type="T">TRACELEVEL = 0</Trace>
<Trace level="3" type="T">EXEMODE = A</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline elements</Trace>
<Trace level="3" type="T">ELEMPOS = 0001</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0002</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0003</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0004</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0007</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0008</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0009</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_RESPONSE</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="1" type="Timestamp">2007-12-27T23:25:53Z 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-12-27T23:25:53Z CET Start of pipeline service processing PLSRVID= PLSRV_MAPPING_REQUEST</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_MAPPING_XMS_PLSRV3</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV">
<Trace level="2" type="T">......attachment XI_Context not found</Trace>
<Trace level="3" type="T">Mapping is already determined in the interface determination</Trace>
<Trace level="3" type="T">Object ID of Interface Mapping 4C27809CF7983547B356B100F7AED5D2</Trace>
<Trace level="3" type="T">Version ID of Interface Mapping 038CECC0946411DCBCA5E2130A0104F7</Trace>
<Trace level="1" type="T">Interface Mapping http://tsfco:I_CRM_SQL_COM_SC:XX:BpFromSqlToCrm SqlToCrmFsCB_IM</Trace>
<Trace level="3" type="T">Mapping Steps 1 JAVA com/sap/xi/tf/_SqlToCrmFsCB_MM_</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/_SqlToCrmFsCB_MM_.</Trace>
<Trace level="2" type="T">Call method execute of the application Java mapping com.sap.xi.tf._SqlToCrmFsCB_MM_</Trace>
<Trace level="2" type="T">Java mapping com/sap/xi/tf/_SqlToCrmFsCB_MM_ completed. (executeStep() of com.sap.xi.tf._SqlToCrmFsCB_MM_</Trace>
<Trace level="3" type="T">Dynamic configuration is empty</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2007-12-27T23:25:53Z CET End of pipeline service processing PLSRVID= PLSRV_MAPPING_REQUEST</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 005</Trace>
<Trace level="3" type="T">Message version 005</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
- <Trace level="1" type="B" name="interface activity determination">
<Trace level="1" type="T">Version 005</Trace>
<Trace level="1" type="T">Message status 009</Trace>
<Trace level="1" type="T">Interface action DEL</Trace>
<Trace level="1" type="T">(must be INIT for a new determination)</Trace>
<Trace level="1" type="T">Set interface action DEL into *MAST*</Trace>
</Trace>
</Trace>
- <Trace level="1" type="B" name="PLSRV_OUTBOUND_BINDING">
<Trace level="1" type="Timestamp">2007-12-27T23:25:53Z CET Start of pipeline service processing PLSRVID= PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
- 
<Trace level="3" type="T">Calling pipeline service: PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_OUTBINDING</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
- <Trace level="1" type="B" name="CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV">
<Trace level="2" type="T">O U T B O U N D - B I N D I N G</Trace>
<Trace level="2" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">determine OUTBOUND BINDING for:</Trace>
<Trace level="2" type="T">-Mrs2sqlq02_BSer</Trace>
<Trace level="2" type="T">-Sys_CR1_120</Trace>
<Trace level="2" type="T">http://tsfco:I_CRM_SQL_COM_SC:XX:BpFromSqlToCrm.CrmReceiver_MI</Trace>
<Trace level="2" type="T">Channel found: - Sys_CR1_120 - Rcv_Sys_CR1_XI</Trace>
<Trace level="2" type="T">no header mapping defined</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2007-12-27T23:25:53Z CET End of pipeline service processing PLSRVID= PLSRV_OUTBOUND_BINDING</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- 
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 006</Trace>
<Trace level="3" type="T">Message version 006</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
- <Trace level="1" type="B" name="interface activity determination">
<Trace level="1" type="T">Version 006</Trace>
<Trace level="1" type="T">Message status 009</Trace>
<Trace level="1" type="T">Interface action DEL</Trace>
<Trace level="1" type="T">(must be INIT for a new determination)</Trace>
<Trace level="1" type="T">Set interface action DEL into MAST</Trace>
</Trace>
</SAP:Trace>

Hi VJ,
After a couple of times it is getting 402 error.
The error node says:
Error when receiving by HTTP (error code: 402, error text: ICM_HTTP_TIMEOUT)
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">CLIENT_RECEIVE_FAILED</SAP:Code>
<SAP:P1>402</SAP:P1>
<SAP:P2>ICM_HTTP_TIMEOUT</SAP:P2>
<SAP:P3 />
Edited by: ashok sri on Dec 28, 2007 8:44 PM

Web service scenario does not work

Hello,
I am prototyping (abap) ws --> PI --> (abap) ws scenario in PI 7.1 with sender and receiver CC of ws adapter.
In the sender system, I coded a abap program to call the proxy to send our ws message, message looks like being sent, in sxmb_moni in the sender system I can see the message, however the status is "Released for processing (WS)", and the sender service of the logged message is empty. In PI, no message is logged in sxmb_moni. Looks like message was sent out from the ws runtime engine of hte sender system, but it didn't reach PI. Does anyone have idea what this is?
Thanks
Jayson

Hi Sukarna,
the connection is not the problem.
Actually I've tested the scenario of abap proxy --> PI -->abap proxy for the same interface, it works fine. Only when I try ws instead of proxy, I got this error. Since proxy scenario works fine, the connection should not be issue.
any more clues?
Thanks

File to File scenario is not working

Hi
I have done simple file to file scenario. I have done all the necessary cofigurations but XI is not picking the file
I have checked in adapter monitoring its saying "File Adapter monitoring is now part of Channel Communication" its not showing any color not in green or not in red its just in default color.
I have cheked in Channel Communication its status is green and log is "Communication Channel is correctly configured and started"
Following are the processing details displayed in Channel Communication
Polling interval started. Length: 5.0 seconds
3/17/08 11:36:19 AM   Processing finished successfully
3/17/08 11:36:19 AM   Processing started
3/17/08 11:36:14 AM   Polling interval started. Length: 5.0 seconds
3/17/08 11:36:14 AM   Processing finished successfully
3/17/08 11:36:14 AM   Processing started
3/17/08 11:36:09 AM   Polling interval started. Length: 5.0 seconds
3/17/08 11:36:09 AM   Processing finished successfully
I Didnt get any messages in Message Monitor and SXMB_MONI.
I checked in default trace and i got following errors
User J2EE_GUEST, IP address
HTTP request processing failed. HTTP error [401] will be returned. The error is [No login module succeeded.No details available].
*Message listener localejbs/TestListener could not be created for connection test after 60 attempts.
Exception getting currently running XMLForm Module version.
java.lang.IllegalStateException: No transaction
at com.adobe.service.J2EEConnectionFactoryManagerPeerImpl.getConnection(J2EEConnectionFactoryManagerPeerImpl.java:70)... [see
Cannot get the name of the EJBean for [email protected]893074.
The error is: java.lang.NullPointerException: null
Exception id: [00114326E0D9004E000005860000072F000448999A01A892
Assertion failed: Logging severity level is not set to 'None'
Assertion failed: Logging severity level is not set to 'None'
Could you please tell me do i need to any other configurations
Regards
Sowmya

Hi
I checked for XIAPPLUSER role in SU01 but it is not there?
What the role of XIAPPLUSER ?
Why do i need this role?
Here we have installed XI in solaries system so i asked my basis team to share one folder in XI system with full access.
First have given transport protocol as the Fil System, at that time communication Channel was in green but i got the above errors which i have mentioned earlier...
My question is can i give the transport protocol as File System because i am accessing the folder with in the XI server but i am accessing it through FTP.
Now i have configured the FTP I have configured everything correct but still i am getting the following errors...
An error occurred while connecting to the FTP server '10.30.3.23:21'. The FTP server returned the following error message: 'com.sap.aii.adapter.file.ftp.FTPEx: 530 Login incorrect.'. For details, contact your FTP server vendor
Could you please help me in this?
Regards
Sowmya

File to idoc scenario error - not working yet :(

Hello! I'm trying to make changes in business partner record in CRM using idoc CRMXIF_PARTNER_SAVE_M01
I have an error 56 EDI: Partner profile not available.
In Control record in we02 transaction, I have right Partner number for Recipient information - logical system name like CRM has in SLD. But there is no Port.
In Sender information I have right Partner number, like my filesystem business system has in SLD and have a port SAPP1D - but I have nowhere entered it!
And one more little question. In we20 transaction am entering inbound parameters for partner:
CRMXIF_PARTNER_SAVE
CRMXIF_PARTNER_SAVE_M
1) Is this right inbound parameters for my idoc?
2) What Process code should I use ?

Hi,
in XI in IDX1 transaction, maintain a port for CRM system specifying the CRM port and the client and the RFC destination from XI to CRM system.......moreover if you are using apply control record values from payload option in reciver IDOC comm channel, then in the IDOC control record in msg mapping map the sender port to CRM port, partner number as logical system of CRM ie C2DCLNT100 and partner type as LS..........then when you will re-run your scenario, your IDOC will have CRM port also in the control record..........
in CRM system your WE20 for LS for XI should have as an inbound parameter your IDOC - which i think you have already done.........
One more thing - put everything in uppercase letters everywhere in msg mapping in control record data, in we20 setting etc.
Regards,
Rajeev Gupta

Save Scenario Script not Working

Hi Gurus,
I have a quick doubt here. Need help on it ASAP. Its been a while since I started with the bookmark functionality.
This is the Error I am getting.
Multiple markers at this line
- Couldn't resolve reference to Member 'saveBookmark'.
- missing ';' at 'Bookmark'
Error if I try running it.
Bookmark an analysis application: SAP BusinessObjects Design Studio 1.3 - YouTube
http://scn.sap.com/community/businessobjects-design-studio/blog/2014/08/04/insides-on-bookmarking
I have gone through all possible links on this, a couple I have provided above, however, I am still not able to
find a solution on it.
The version details of the tool used are here.
SAP BusinessObjects Design Studio
Release 1.3 (Version: 13.0.3.201405141058)
I am using the BW queries and its run on netweaver portal.
What could be the issue?
Thanks in advance.

Hi Sateesh,
The ";" is a part here,in a hurry I dint include it. Actually the same function is working Locally but in netweaver it isnt.
var name = INPUTFIELD_NAME.getValue();
Bookmark.saveBookmark(name);
//The rest of the code populates the dropdown menu and clears the value of the input field.
/* get all Bookmarks */
var bookmarks = Bookmark.getAllBookmarks();
bookmarks.forEach(function(element, index)
BOOKMARK_DROPDOWN.addItem(element.name, element.text);
INPUTFIELD_NAME.setValue("");
I think its some BW plug in issue. Is that so?
Thanks,
Sara

HTTP(s) - RFC - HTTP(s) scenario is not working synchronous.

Dears,
I have the following scenario.
our PI system will receive an XML over HTTP(s) from outside company.
and then our system will send a confirmation to that company.
I already configured it with synchronous outbound Interface.
Now, I can post xml to PI URL . and it reached RFC but no response.
I checked the SAP XI runtime workbench - adapter logs and i found :
RfcAdapter received a asynchronous message. Trying to send tRFC for YISU_SAPI_BCONRQ with TID XI051MbW017j2emZuP2jN5nm.
RfcAdapter received a asynchronous message. Trying to send tRFC for J2EE_GUEST with TID XI051MbW017j2emZuP2jN5nm.
My interface is synchronous but in the logs showed asynchronous!!!!
What is the problem????
Thanks and Regards,

http://****:50000/sap/xi/adapter_plain?namespace=urn%3ASALE_P&interface=SI_SALE_OB&service=CC_SALE&party=&agency=&scheme=&QOS=EO&sap-user=***&sap-password=***&sap-client=240&sap-language=EN
just remove the QOS itself. By default it is BE
http://***:50000/sap/xi/adapter_plain?namespace=urn%3ASALE_P&interface=SI_SALE_OB&service=CC_SALE&party=&agency=&scheme=&sap-user=*&sap-password=**&sap-client=240&sap-language=EN
refer;
http://help.sap.com/saphelp_nw04/helpdata/en/43/64db4daf9f30b4e10000000a11466f/frameset.htm

File2File scenario is not working

Hi,
I configured the File to File scenario which has given in the Weblog.
I done exactly the way in the weblog and activated everything.
But the scenario is executed, I have checked in the message monitoring no messages in it.
My File Adopter spooling interval is 60s.
Can anybody tell me the procedure to execute a scenario.
Thanks
Srinivas Sandaka

Hi,
Thanks for you quick response.
Adapter in RWB in green status.
Environment->Cache
     Cache Update Status is in red status
     Perform Notification status is in green.
Pool interval is 2 seconds.
Processing mode is delete.
In the file Adapter testing the following fields are mandatory.
          Send Message To, Sender, Interface,
           Namespace, Quality of Service.
can you give me the which objects I have to give in thier fields.
Thanks
Srinivas Sandaka

Again after last patch: Windows 64 - PDF preview handler not working

Adobe's PDF preview handler doesn't work unter Windows XP/Vista/7 64 bit. Because of that PDF preview e.g. in Windows explorer or MS Outlook isn't displaying PDF preview.
This issue has been discussed in this forum some months ago, and this page gives a solution that has helped:
http://www.pretentiousname.com/adobe_pdf_x64_fix/index.html#fixer
Instead of fixing this well-known issue with the last patch Adobe decided again not to fix. And after installing the patch you have to repair PDF preview handler again...
Friendly
Philipp
Philipp
http://ferienbretagne.livejournal.com
Lenovo W500, 2,8 Ghz T9600, 8GB RAM, Windows 7 Pro 64-Bit, Acrobat 9

Hi Sree,
According to your description, your case related to Adobe PDF Preview Handler. This is third-party product. I am afraid this is out of our support. Please ask in their special forum
https://forums.adobe.com/community/adobe_reader_forums
By the way, after do some search, it seems not working for 64bit machine,
>> It is working fine in Windows 7 and Vista
Also work fine in win7/vista 64bit????
If your scenario is not working in 64bit machine, try to put "adobe pdf preview handler 64-bit fix" in search engine. Good luck.
Have a nice day!
Kristin
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Restore Tablespace incremental backup is not work as after reimage oracle

TheTablespace incremental backup Restore is not work as after reimage the oracle database or restore tablespace in standby machine(another machine) is not working .its working in the same machine without reimage .after reimage not working please clarify me ,
I need the solution as soon as please reply as soon as .
Commnads used:
This is the step is followed but i am getting backup or control file not found error.Its works i the application server is not reimaged ;
please give your valuable suggestion .
Product Used:oracle 11g in linux environmnet
1)Before taking backup get SCN number for restore.
Command applied: Select current_scn from v$database;
2)running Full backup of database
Command applied:
configure controlfile autobackup on;
backup database plus archivelog;
CROSSCHECK BACKUP;
exit;
3)Running level 0 incremental backup
Before taking backup get SCN number for restore.
Command applied:
BACKUP AS COMPRESSED BACKUPSET INCREMENTAL LEVEL 0 TAG ='WEEKLY' TABLESPACE TEST;
exit;
3) Running level 1 incremental backup
Before taking backup get SCN number for restore.
Command applied:
BACKUP AS COMPRESSED BACKUPSET INCREMENTAL LEVEL 1 TAG ='DAILY' TABLESPACE TEST;
4)Before Restore(TSPITR) following procedure are applied under sysdba privilege
Command applied:
SQL 'exec dbms_backup_restore.manageauxinstance ('TSPITR',1)';
5)TSPITR Restore command
Command applied:
run
RECOVER TABLESPACE TEST UNTIL SCN 1791053 AUXILIARY DESTINATION '/opt/oracle/base/flash_recovery_area';
SQL 'ALTER TABLESPACE TEST ONLINE';
please calrfiy my following question:
1. After reimage(reinstall oracle database with application ).The aboove scenario is not working
2. After fullbackup what are the files needs to copy from (opt/oraclle/base/flash_recovery_area/dbname/) to repository because daily cleanup script will keep the data as sysdate -1 .
For fullbacckup we are currently copying entire (flash_recovery_area/dbname) database folder to repoistory.
3. after incremental backup what are the files needs to copy from (opt/oraclle/base/flash_recovery_area/dbname/..) to repository because daily cleanup script will keep the data as sysdate -1
For incremenatl backup currently we are copying (flash_recovery_area/dbname/backupset/<currentdate> and flash_recovery_area/dbname/autobackup/<currentdate>) folder to repoistory.
4.During restore we are copy entire things from repository to flash_recovery_area finaly apply the above mentioned restore command.
Tabelspace incremenatl restore is possible after reimage application server(fresh database)/another server with same database(standby machine) ....?
If we missing something in backup side please clarify me how to retore the tablespace incremental / level 0 tablespacae after reinstallion of server/another standby server.
Any information please let me know .I need the solution as soon as please reply as soon as .

Try the Recovery Manager (RMAN) instead. This forum is for feedback about the 11g XE Beta.

"Find Form" calendar is not working after migration

Hi,
We have migrated from Oracle 9i to 10g.we have one form ''FormA" and "find form" for that FormA.Calendar functionality is present in both FormA and "Find FormA".if we try to use calendar functionality in "Find formA",its giving error like FRM-40104 - No such block calendar,FRM-40105(unable to resolve reference to item claendar.cell1.........),FRM-41045 (cannot find item - invalid id).Actually this scenario is not working after migrating the FORMS application to 'OAS10.1.2' from 'OAS904' .
In 'OAS904' ,The calendar item is present in the 'FormA' form, the 'calendar.show' hides the "Find FormA" and appears in the FOrmA and uses FormA's calendar item and after selecting the date,the date s applied to the "Find FormA"
But after migration, the "Find FormA" is not hiding, so its not able to retrieve the calendar properties.Because the calendar is present in "FormA".
Any problem with pll files like 'qmslib65','qmsolb65',qmsevh65'??
please help me by providing suggestions.
Thanks

qmslib65','qmsolb65',qmsevh65Are these libraries self-written or from some third-party tool?

ASMA not working

Hi ,
We have a scenario where Sender is AS2 and Recievr is FILE . We need the file name to be same as the sender adapter picks it.
I have clicked the ASMA tab and also FILENAME on the reciever side.
The ASMA doesnt seem to work.
Please suggest a solution..
Appreciate your quick help..
Thank you
Yashwanth

Hi All,
Thanks for your response.
There is no mapping involved in this scenario.
The below modules have been in the sender AS2 adapter.
1     localejbs/Seeburger/solution/as2     Local Enterprise Bean     solutionid
2     localejbs/CallSapAdapter     Local Enterprise Bean     exit
The reciever is a simple FILE adapter and is using the below modules :
1     AF_Modules/DynamicConfigurationBean     Local Enterprise Bean     getFileName
2     AF_Modules/DynamicConfigurationBean     Local Enterprise Bean     setFileName
3                   CallSAPAdapter
Also there are keys to get and set the file name in the module configuration.
Still the scenario is not working.
We have another interface with exactly the same settings and it is working perfectly fine.
Please suggest.
Yash

B1SO2B1PO scenario is not working

Similar Messages

Maybe you are looking for