Error - Distributing the Model using BD64

Hi! All
Not able to distribute the model from the Sender System.
Error : Model view ZDMKANBAN has been changed
While Generating the Partner Profile able to generate Partner, Port, Outbound parameter from the Sender System.
but if i execute an IDOC through WE19 able to get the Status - 03 for Sender System & Status - 53 for Receiver System
when i try to transfer IDOC from Sender System to Receiver System could not do it.
Hope so bz of error occurred in Distribution Model. Is it So
kindly help me.

you have to distribute the distribution model in its new version

Similar Messages

Error while distributing the model

Hi
I am not able to successfully distribute my model thru BD64. I am getting the error msg as ' the model has not been updated'.The configuration done till now is according to the basic procedure.
Can anyone please suggest a way to overcome this error.
thanks

Hi,
You can create a distribution model and then add message type to it; however, there are some preconditions which you need to ensure before you create the model.
Preconditions:
1) Ensure that you have the message type in both the systems; if custom msg type is used, you need also to create the one in the partner system.
2) Do all configuration related to msg type, idoc type, etc in your partner system as well
3) Create RFC destination in the current system for your partner system... and test the connection if it is working fine
After you create the model and added msg type to it, you also need to do the following:
1) Go to Edit --> Model View --> Distribute to distribute/ create it in your partner system
2) To validate, you can check in your partner system if the model is automatically created there
3) Then create Partner profile in both the systems by going to Environment --> Generate Partner Profiles
Hope it helps and solves your problem.
Regards, Tapas
<Pls award pts if useful or answered>

Error in Distributing the model view

Hi,
I have clients 600, 610 & logical systems (ls_600, ls_610) in the same system.
I am trying to set up the ALE customizing and distribute the model view.
I have created RFC from 600 to 610 and the test connection is fine.
I have created a model view in which i have given sender system as LS_600 and
receiver system as LS_610 and the message type as MATMAS.
In the partner profile(WE20) of LS_610(client 600), in the outbound parameter SYNCH
i have given a port which uses the RFC to 610.
When i have tried to distribute the model view it is giving error as
'communication error occured. Username or password is not correct (Repeat Registration).'
I am not able to figure out the error.
There is also a partner profile as ls_600. Do i have to
make any changes there ?
Do i have to do something in the client 610 ?
Your help is highly appreciated.
Thanks,

Hi Prasad,
Please maintain the MATMAS & SYNCH Message type in the Outbound partner profiles of LS 610.
Test distributing the MATMAS IDoc's using BD10 without even maintaining Distribution Model.
And let me know if you are able to distribute the IDoc or not.
If you get the error. Please let me know the error.
Regards,
Krishna

IDoc to IDoc scenario: distribute the model view

Hi!
I try currently to configure a IDoc to IDoc scenario for SAP ECC 6.0 system with following business 2 systems:
ERP:100 (Sender)
ERP:200 (Receiver)
and XIB:100 (XI system)
I successfuly created a message type and generated the model view in tcode BD64.
Question:
When I try to distribute the model view which system should I choose?
a) XI System or
b) Receiver system ERP:200
When I choose the receiver system ERP:200 and get the following error
Target system: ERP:200
Model view ECCCLNT100 has not been updated
Reason: Distribution model is currently being processed
When I try to choose my XI system I get the following error:
Target system: XIB:100
RFC destination for synchronous communication (message type SYNCH)
Partner profile LS PIBCLNT100 SYNCH does not exist
Generate partner profile
or specify outbound partner profiles for message type SYNCH
Is that an error? If yes, how can I fix them?
Thank you very much
Thom

Hi
Look my reply on this thread regarding SYNC Message Type.
Re: problem while distribute model view
When I try to distribute the model view which system should I choose?
a) XI System or
b) Receiver system ERP:200
You are sending IDoc to XI then R/3 so select XI system. because receiver of IDoc is XI then IDoc would be send from XI.

Not able to distribute the model

Hi
I created a model using BD64 according to the procedure to the best of my knowledge. But i am getting the following error
"Model view has not been updated. Reason: the distribution model is currntly being processed."
Nobody else are logged in. Can anybody say what the prob might be and how can that be solved

hi
check this link
[Re: getting problem while creating the dist model in bd64|Re: getting problem while creating the dist model in bd64]
Thanks& Regards
Nagesh.Paruchuri

Unable to distribute the MODEL to backend system in SRM 5.0

Hello Experts,
I have created distribution model " SRM_to_R3" in BD64, maintained message types BBPCO, BBPIV and MBGMCR
Every time I try to Distribute this MODEL to back end system I get the following error in IDES system
Target system T90CLNT090       Commnunication error occurred, error when opening an RFC connection
RFC connections are
T90CLNT090   - SRM to R3
SRM_00_800   - R3 to SRM
Systems got connected successfully and I can "Remote Logon" too......
My query is why am not able to send or distribute the MODEL from SRM to ECC backend system ?
How to get rid of the error and successfully distribute MODEL to backend system.........appreciate your help in this regard
Rgds !
SAP Novice

Hi Zuljana,
Kindly check if your partner profile is active. (Indicated by 'A')
Sometimes if your partner profile is not active, you wont be able to distribute your model. Check the 'A' indicator
Regards,
Nikhil
Edited by: Pbponikhil on Dec 21, 2010 4:11 PM

WhAT Is distributing the model

Hi All
Can anybdy plzz explain me what do we mean when we say we distribute the distr model in bd64?

Hi
The distribution model describes the ALE message flows between logical systems.
<b>Use</b>
You can specify the relationships between logical systems, message types, BAPIs and filters in the distribution model. Applications and the ALE layer use the model to determine receivers and to control the data distribution.
<b>Structure</b>
In the distribution model you can specify the messages to be sent to a given logical system. You can also define the conditions for the content and dispatch of messages in the filters.
The distribution model consists of one or more views that you can define. With more complex distribution tasks you can assign business sub-areas or groups of logical systems to separate views.
The relevant views of the distribution model must be available in all the logical systems involved in ALE. You can find the functions for distributing views in Customizing for ALE.
Hope this helps.
Regards
Sumit Jain
**Reward with poitns if useful

Error message: The preset used by one or more sequences in this project requires third-party components that could not be located. These sequences will be modified to use a custom sequence setting instead. To continue editing using the original preset, qu

Hello all,
I can't open a PP project without this error message appearing:
"The preset used by one or more sequences in this project requires third-party components that could not be located. These sequences will be modified to use a custom sequence setting instead. To continue editing using the original preset, quit the application without saving the project, reinstall any third-party components that are required and reopen the project".
What I had been doing before this occurred was editing a PP project using ProRes sequences and multi-camera editing. Multi-camera was not working very well and after a few attempts to fix that I gave up and finished the job cutting 3 layers of video instead. AME refused to render the three finished sequences of over 1hr duration so rendered final videos from the PP sequences.
I tried deleting plists for AME, PP and QT, repairing disc permissions and rebooting but there was no improvement.
Client is satisfied for now but will want to come back to this job at a later date so decided to uninstall and re-install AME and PP in the hope both would be ready to work properly when needed again. AME works fine in conjunction with a different PP project but now I can't open the PP project in question without the above error message appearing.
Having searched the net it would seem that the problem may be caused by ProRes but I haven't been able to find a definitive solution for the problem. Does anyone know either:
1. How to fix this?
2. If I chose the "modified using a custom sequence setting", can I be sure that my sequences will look the same even if they don't use ProRes? The final deliverable format will be mp4 so as long as the overall look doesn't change then I can afford a change in the edit codec. It's just that with three sequences over an hour long, I don't want days of work to be ruined.
Other older PP projects of mine open and work fine.
Premiere Pro CC 8.2.0
Media Encoder CC 8.2.0.54
OSX 10.10.2
Any help would be greatly appreciated.
Duncan.

Adobe web chat come up with a solution.
Open the PP project.
Export your sequence or project as a Final Cut Pro XML file.
Set up a new PP project.
Import the Final Cut Pro XML file.
This will get you back up an running.
Since getting back to editing this project I have found that some things will be lost or change in using XML:
You will lose position key framing, black video clips, dissolve fx, audio levels, audio dynamic fx, the ability to open a multi camera clip and change the camera view.
You will keep cut points, crop fx.
Not perfect but only took a couple of hours to save 3 days work.

Hide an error from the application using a servererror trigger?

We have an application designed for an old oracle version which issues some sql which is no more supported in todays database version.
We want to use the application unchanged with a new database server.
Old Server Version: 7.3.4 (still in production...)
New Server Version: 10.2 or 11.2
The application issues an
ALTER SESSION SET OPTIMIZER_GOAL = FIRST_ROWS ;
which results in ORA-01986 and the application dies.
We would like to hide the error 01986 from the application using a trigger:
create or replace
trigger catch01986
after servererror
on schema
begin
    if (ora_is_servererror (1986)) then
      null; -- what to do here? we want clear the ora-01986 from the error stack
    end if;
end catch01986;How to handle the error, so that the alter session set ... statement is just ignored and no error code is returned to the application?
I asked already some days ago in Database-General Forum, but triggers belong to PL/SQL, so i repost here.
Tnx for help in advance!

Hi,
hoek wrote:
A totally weird and untested (and unable to test today) thought:
http://technology.amis.nl/blog/447/how-to-drive-your-colleagues-nuts-dbms_advanced_rewrite-oracle-10g
Very interesting for real dirty solution.
Does not work for my problem, DBMS_ADVANCED_REWRITE works only for select statements.
BEGIN
   SYS.DBMS_ADVANCED_REWRITE.DECLARE_REWRITE_EQUIVALENCE (
   'alter_session_equivalence',
   'ALTER SESSION SET OPTIMIZER_GOAL = FIRST_ROWS',
   'ALTER SESSION SET OPTIMIZER_MODE = RULE',
   FALSE);
END;
ORA-30389: the source statement is not compatible with the destination statement
ORA-00903: invalid table name
ORA-06512: at "SYS.DBMS_ADVANCED_REWRITE", line 29
ORA-06512: at "SYS.DBMS_ADVANCED_REWRITE", line 185
ORA-06512: at line 2
30389. 00000 - "the source statement is not compatible with the destination statement"
*Cause:    The SELECT clause of the source statement is not compatible with
           the SELECT clause of the destination statement
*Action:   Verify both SELECT clauses are compatible with each other such as
           numbers of SELECT list items are the same and the datatype for
           each SELECT list item is compatible
hoek wrote:You already had some trigger code, catching the error and sending it to null, why didn't that work?The trigger is fired when the error occurs, but after completion of the trigger, the error code is still delivered to the client.
I dont know how to handle the error within the trigger.
Does the client read the error stack and does it die after reading an error from the stack?The client just checks the error code. On error it terminates.
With the SERVERERROR TRIGGER i did the following tests:
Test 1: trigger does nothing
CREATE OR REPLACE
TRIGGER CATCH01986
AFTER SERVERERROR
ON SCHEMA
BEGIN
    IF (ORA_IS_SERVERERROR (1986)) THEN
      NULL;
    END IF;
END CATCH01986;
ALTER SESSION SET OPTIMIZER_GOAL = FIRST_ROWS;
ORA-01986: OPTIMIZER_GOAL is obsolete
01986. 00000 - "OPTIMIZER_GOAL is obsolete"
*Cause:    An obsolete parameter, OPTIMIZER_GOAL, was referenced.
*Action:   Use the OPTIMIZER_MODE parameter.
-- Client Application reports errorcode 1986Test 2: Trigger raises NO_DATA_FOUND
CREATE OR REPLACE
TRIGGER CATCH01986
AFTER SERVERERROR
ON SCHEMA
BEGIN
    IF (ORA_IS_SERVERERROR (1986)) THEN
      RAISE NO_DATA_FOUND;
    END IF;
END CATCH01986;
ALTER SESSION SET OPTIMIZER_GOAL = FIRST_ROWS;
ORA-04088: error during execution of trigger 'AH.CATCH01986'
ORA-01403: no data found
ORA-06512: at line 9
ORA-01986: OPTIMIZER_GOAL is obsolete
04088. 00000 - "error during execution of trigger '%s.%s'"
*Cause:    A runtime error occurred during execution of a trigger.
*Action:   Check the triggers which were involved in the operation.
-- Client Application reports errorcode 4088Test 3: Trigger raising an APPLICATION ERROR
CREATE OR REPLACE
TRIGGER CATCH01986
AFTER SERVERERROR
ON SCHEMA
BEGIN
    IF (ORA_IS_SERVERERROR (1986)) THEN
        DBMS_STANDARD.RAISE_APPLICATION_ERROR(-20999, 'this makes no sense', true);
    END IF;
END CATCH01986;
ALTER SESSION SET OPTIMIZER_GOAL = FIRST_ROWS;
ORA-00604: error occurred at recursive SQL level 1
ORA-20999: this makes no sense
ORA-06512: at line 10
ORA-01986: OPTIMIZER_GOAL is obsolete
00604. 00000 - "error occurred at recursive SQL level %s"
*Cause:    An error occurred while processing a recursive SQL statement
           (a statement applying to internal dictionary tables).
*Action:   If the situation described in the next error on the stack
           can be corrected, do so; otherwise contact Oracle Support.
-- Client Application reports errorcode 604Test 4: Adding an EXCEPTION part to the trigger does not help, this will catch only exceptions raised while the trigger executes:
CREATE OR REPLACE
TRIGGER CATCH01986
AFTER SERVERERROR
ON SCHEMA
BEGIN
    IF (ORA_IS_SERVERERROR (1986)) THEN
        DBMS_STANDARD.RAISE_APPLICATION_ERROR(-20999, 'this makes no sense', true);
    END IF;
EXCEPTION
    WHEN OTHERS THEN
      NULL;
END CATCH01986;
ALTER SESSION SET OPTIMIZER_GOAL = FIRST_ROWS;
ORA-01986: OPTIMIZER_GOAL is obsolete
01986. 00000 - "OPTIMIZER_GOAL is obsolete"
*Cause:    An obsolete parameter, OPTIMIZER_GOAL, was referenced.
*Action:   Use the OPTIMIZER_MODE parameter.
-- Client Application reports errorcode 1986So i do not know what to do inside the trigger to clean the error stack so that the client will receive no errorcode.

Error in distributing the Model View in BD64

Hi Experts,
I have some problem in distributing model view in BD64. please see here the error details:
Model view <logical client> has not been updated
Reason: No authorization to create model view <logical client>
.....authorization object B_ALE_MODL
.....Parameter: activity 01, model view <logical client>
i have created full auth and B_ALE_MODL role for the specific account but still i cant proceed.
Please help.
Thank you,
Tony

Hi Experts,
In addition, this is in line with our integration between SRM 7.0 EHp1 SPS05 and ECC 6.0 EhP4 SPS03. both systems are running in windows 2003 64bit.
Edited by: Tony on Aug 3, 2011 4:30 AM

11.1.1.4 - MDS-00068 Error for the Application using user customization

Hi All,
I would like to check on this forum before I submit a SR. We have upgraded our ADF APP from 11.1.1.3 to 11.1.1.4. Many bugs are fixed, however while deploying the application we get following warning on integrated WLS Logs and application deployed successfully. The same app is working ok in 11.1.1.3. Also, if I deploy this application on Standalone WLS server and try to go to Enterprise Manager MDS configuration page for this Application it gives me a message - "MDS configuration information is not found. This application does not use MDS repository or MDS repository may not have been configured properly".
Any help would be appreciable.
- Chetan
<ADFConfigLifeCycleCallBack> <contextInitialized> Failed to create config mbean.
oracle.mds.exception.MDSRuntimeException: MDS-00068: Unable to find a type definition for: namespace = http://xmlns.oracle.com/adf/config, local name = caching-rules, file location = /META-INF/adf-config.xml
     at oracle.mds.core.MOTxnState.getMElemBean(MOTxnState.java:207)
     at oracle.mds.core.UpdateableMOContent.getMElemBean(UpdateableMOContent.java:611)
     at oracle.mds.core.MetadataObject.getContentWithRetry(MetadataObject.java:2039)
     at oracle.mds.core.BeanMetadataObject.getBean(BeanMetadataObject.java:89)
     at oracle.adf.share.jndi.MDSBackingStore.getMOBean(MDSBackingStore.java:570)
     at oracle.adf.mbean.share.config.RuntimeMXBeanImpl.init(RuntimeMXBeanImpl.java:169)
     at oracle.adf.mbean.share.config.RuntimeMXBeanImpl.<init>(RuntimeMXBeanImpl.java:159)
     at oracle.adf.mbean.share.config.RuntimeMXBeanImpl.<init>(RuntimeMXBeanImpl.java:151)
     at oracle.adf.mbean.share.config.ADFConfigLifeCycleCallBack.contextInitialized(ADFConfigLifeCycleCallBack.java:127)
     at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
     at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
     at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1872)
     at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
     at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
     at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
     at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
     at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
     at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
     at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
     at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
     at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
     at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
     at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
     at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
Caused by: oracle.mds.exception.MDSRuntimeException: MDS-00068: Unable to find a type definition for: namespace = http://xmlns.oracle.com/adf/config, local name = caching-rules, file location = /META-INF/adf-config.xml
     at oracle.mds.internal.model.parse.MDSNodeParser.findMMElement(MDSNodeParser.java:322)
     at oracle.mds.internal.model.parse.MDSNodeParser.createModelNode(MDSNodeParser.java:603)
     at oracle.mds.internal.model.parse.MDSNodeParser.startElement(MDSNodeParser.java:240)
     at oracle.mds.internal.parsefwk.TreeBuilder$Handler.startElement(TreeBuilder.java:298)
     at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1329)
     at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:376)
     at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:322)
     at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:226)
     at oracle.mds.internal.parsefwk.TreeBuilder.parse(TreeBuilder.java:143)
     at oracle.mds.internal.parsefwk.TreeBuilder.parse(TreeBuilder.java:105)
     at oracle.mds.internal.model.parse.SAXParserUtils.parse(SAXParserUtils.java:479)
     at oracle.mds.internal.model.parse.SAXParserUtils.parse(SAXParserUtils.java:419)
     at oracle.mds.internal.model.parse.SAXParserUtils.parseBaseDocument(SAXParserUtils.java:114)
     at oracle.mds.internal.model.BaseDocBuilder.executeInternal(BaseDocBuilder.java:336)
     at oracle.mds.internal.model.BaseDocBuilder.execute(BaseDocBuilder.java:172)
     at oracle.mds.internal.model.ContentModelPipeline.processPipeline(ContentModelPipeline.java:265)
     at oracle.mds.core.MOContent.fetchContent(MOContent.java:510)
     at oracle.mds.core.CachedMOContent.fetchContent(CachedMOContent.java:253)
     at oracle.mds.core.MOContent.getMElemBean(MOContent.java:688)
     at oracle.mds.core.UpdateableChainedMOContent.getPriorModelDocument(UpdateableChainedMOContent.java:322)
     at oracle.mds.core.UpdateableChainedMOContent.fetchContent(UpdateableChainedMOContent.java:266)
     at oracle.mds.core.MOContent.getMElemBean(MOContent.java:688)
     at oracle.mds.core.MOSharedState.getMElemBean(MOSharedState.java:124)
     at oracle.mds.core.MOTxnState.getMDocumentInternal(MOTxnState.java:384)
     at oracle.mds.core.MOTxnState.getMElemBean(MOTxnState.java:200)
     ... 45 more

Hi Frank,
I was able to solve the issue after isolating it to ADF faces caching filter. We are using ADF faces caching filter for our application and we have defined <caching-rules> tag in adf-config.xml file. I found that <caching-rules> was part of the schema definition of namespace "http://xmlns.oracle.com/adf/config" till 11.1.1.3 and now in 11.1.1.4 it is not anymore and that's why just specifying <caching-rules> tag was working in 11.1.1.3.
To solve the error I changed caching-rules to read from http://xmlns.oracle.com/adf/faces/rich/acf namespace. Now my caching rule tag in adf-config.xml looks like given below.
<caching-rules xmlns="http://xmlns.oracle.com/adf/faces/rich/acf">
<caching-rule id="cache-js">
<cache>true</cache>
<compress>true</compress>
<duration>99999</duration>
<agent-caching>true</agent-caching>
<cache-key-pattern>*.js</cache-key-pattern>
</caching-rule>
<caching-rule id="cache-png">
<cache>true</cache>
<compress>true</compress>
<duration>99999</duration>
<agent-caching>true</agent-caching>
<cache-key-pattern>*.png</cache-key-pattern>
</caching-rule>
<caching-rule id="cache-css">
<cache>true</cache>
<compress>true</compress>
<duration>99999</duration>
<agent-caching>true</agent-caching>
<cache-key-pattern>*.css</cache-key-pattern>
</caching-rule>
</caching-rules>
- Chetan

Prob in distributing the model

Hi
Being done with the initial steps, I created the distribution model
When i distribute that , i get the error stating "Communication error , function xxxxxxxxxx is not available".
Due to what reson this error could be? Kindly elaborate .
Thanks

Hi,
1.Check in the SM59.That error due to the RFC destination is not correctly assigned.
2.Check both sides in outbound and inbound.
Regards,
Kumar(Reward if helpful).

Error in the Query used in APEX_COLLECTION.CREATE_COLLECTION_FROM_QUERY_B

Dear All,
I am using the following in a PL/SQL Before Header process.
Please help me with the following :
APEX_COLLECTION.CREATE_COLLECTION_FROM_QUERY_B ('LEASE', 'SELECT LSE_NUM
                                                                                                   FROM   RE_LEASE
                                                                                                   WHERE LSE_COM_NUM = :P0_COM_NUM');I am getting the following error:
ORA-20104: create_collection_from_query_b Error:ORA-20104: create_collection_from_query ExecErr:ORA-01008: not all variables bound
If I change the above as
APEX_COLLECTION.CREATE_COLLECTION_FROM_QUERY_B ('LEASE', 'SELECT LSE_NUM
                                                         FROM   RE_LEASE
                                                         WHERE LSE_COM_NUM = ' || :P0_COM_NUM);Then I get the following error :
ORA-20104: create_collection_from_query_b Error:ORA-20104: create_collection_from_query ParseErr:ORA-00936: missing expression
I am using the above to create Next and Previous buttons using the reference provided by ATD in the Re: How to do page break
Note: If I do not use any Items in the WHERE as below then I do not get any errors and it works as required.
APEX_COLLECTION.CREATE_COLLECTION_FROM_QUERY_B ('LEASE', 'SELECT LSE_NUM
                                                                                                  FROM   RE_LEASE');I want to use Items in the query for the collection. Please help.
Best Regards
Arif Khadas

Hi Jari,
Thanks Jari for the reply. Your solution does work as well but please if you can throw some more light on q'! (first line) and !' (last line).
q'!
SELECT LSE_NUM
   FROM   RE_LEASE
WHERE LSE_COM_NUM = (SELECT v('P0_COM_NUM') FROM DUAL)
!'Best Regards
Arif Khadas

Error configuring the repository using Repository Assistant.

Hi,
I have a SYSDBA access to a oracle 9i instance and i tried to configure the OWB Repository through Repository Assistant. I am getting the following error.
How can i rectify this error.
INS0037 - The initialization parameter job_queue_processes of the Database <instance_Name> cannot be set to zero. the recommended value for OWB is 10 or larger. Please change the parameter settings in the database, then coontinue the repository installation.
Thanks and Regards,
Soma

Hi Soma,
you have to set the parameter job_queue_processes for your db to 10 or larger.
In advance verify with your dba that the parameter is not set to zero on purpose to prevent other jobs from running!
Regards,
Carsten.

Error while distributing a distribution model in BD64

Hi,
I am trying to send an IDOC from one client to another client of the same SAP system. To achieve that, i have created the necessary logical systems and made the necessary partner, port configuration as well as RFC Destination. In BD64, I have created a new model and added a BAPI 'SAVEREPLICA' and Object 'BUS1093' using Add BAPI button. But when I am trying to distribute the model it's giving the following error - 'Model view ABCDX has not been updated. Rreason: Distribution model is currently being processed'.
Kindly help,
Thanks in advance,
Deep.

Using of BAPI is not accepted between two clients of the same system, you'll have to use different SAP systems

Error - Distributing the Model using BD64

Similar Messages

Maybe you are looking for