ERROR DURING T.CODE F-53 ( cross company transaction error)

Hello ,
I am clearing two documents , in which one is cross company code transaction and another is vendorinvoice through t.code f-53.
while saving the document I am gettting the following error.
Consolidated companies 1000 and ' ' are different
Message no. F5080
Diagnosis
The number of the affiliated company must be clear for the selected document type for all line items. In this case at least two different companies or a company in connection with a business partner who does not belong to a company are stated.
Procedure
If you selected the correct accounts, you must enter the document with a document type that allows cross-company posting. Otherwise, please correct the entered account.
kindly help me to solve this issue
thanks and Regards,
muscan

Hi,
Please check if in the control data of the vendor master "Trading Partner" is populated.
If yes, then if you remove the trading partner then you might not get this error.
If a trading partner is there, the system check the document type for Intercompany posting control and if its not there then the system gives such an error.
Changing a document type might impact all the business transactions relating to the document type that you are using.
However this might not be required in your scenario.
Thanks,
Nitish

Similar Messages

Using PO or DO as reference during STO and STO return - cross company

Hi,
May I have your valuable input of which of the following are the best practise in term of the two business process:
A - cross company stock transport order during goods receipt, and,
B - cross company stock return order during goods receipt
FYI, I am talking about two-steps procedure (i.e. movmt type 643 and 101)
Question:
For A -
During Goods rececipt will it be BEST to use a purchasing order OR the outbound delivery order as a reference?
My gut feeling is using outbound delvery document as reference, but what is the underlying reason to do this, why not PO?
For B -
During Goods rececipt will it be BEST to use a purchasing order OR the outbound delivery order as a reference?
My gut feeling is using PO document as reference, but what is the underlying reason to do this, why not delivery order?
I read the SAP help portal, it said in return process, it is best use PO because of this statement (i.e. Do not post with reference to the delivery, so that the delivery for the stock transport order is not updated), which I don't quick get it.
Hope you can shed some light.
thanks
tuff

Hi,
If your PO (sto) is of 100 quantities and the outbound delivery is created for only 80 quantities, So when you do a GR against outbound delivery you will be doing directly for 80 quantities. But if you are doing it against the PO, all the 100 quantities will show up and then you have to manually reduce the 20 quantities.
For the return process there may be a constraint as when you do a return against delivery it may not open the PO but when you do it against PO it would be updated and can be seen in the PO history and you can also see the open po quantity.
More inputs on this are welocme.
Thanks,
Atal

Inter Company Transactions Error

Dear Experts,
While posting an inter Company transaction, the following error is confronted with:
A unique company code has not been assigned to company number XXXXXX
Message no. GLT0001
Diagnosis
Document breakdown is active in your system. In certain cases, a company code is derived from the company ID number, and this must lead to the assignment of a unique company code.
A unique company code could not be assigned to company number XXXXXX.
System Response
You cannot carry out the required posting.
Procedure
Assign one company code to company number XXXXXX.
We are working on ECC 6 and New GL is activated. Both the Company codes considered in the transaction have been assigned to the same Company. The required setting is maintained in OBYA. Also the Inter Company postings is ticked in the document type used.
Kindly let me know what is the gap for this error.
Best Regards,
Srini

The problem is you need to create COMPANY and assign the same to both company codes in OBY6.
The following information must be useful.
You can post the cross company code postings even between two controlling areas. The system does not prevent to post documents between two company codes in two controlling area. Need not necessarily they should be under one operating concern. Provided you have to make sure that you have followed the following points:
In OBY6 - To company codes must be assigned to same Company, meaning that you mus thave created a Company and that company must have been assigned to these two company codes.
OBYA - You should maintain the clearing accounts in both the company codes. Meaning that you are posting one leg in one company code and the other leg in the other company. Therefore, it is required to have the missing legs in each company code.
Company Code1 - Posting Key 40 - Clearing Account
Company Code1 - Posting Key 50 - Clearing Account
Company Code2 - Positng Key 40 - Clearing Account
Company Code2 - Posting Key 50 - Clearing Account
OB08 - In case if the two company codes have different local (company code) currencies, you may maintain the exchange rates.
You can now go to F-02 and post a cross company code transaction giving the first leg in first company code and the second leg in second company code. Missing leg in the first company code will be posted to the GL Account mentioned in OBYA and the missing leg in the second company code will be posted to the GL Account mentioned in OBYA. That means you will have four line items overall.
The system will post three document.
Document 1 in First Company Code
Document 2 in Second Company Code
and
Document3 - Cross Company Code Document.
The cross company code document consists of the first company code document number plus company code plus last two digits of the fiscal year.
Hope this must have clarified your doubts.
Please let me know in case if you need further details.
Thanks,
Ravi

Posting of cross company transaction with different doc types

Hi,
The scenario is:-
We have two companies X and Y.
X makes a payment to Y with the following FI entries:-
Company Code X
Dr Vendor Y
Cr Bank HDFC
Company Code Y
Dr Bank ICICI
Cr Customer X
Now this needs to be a cross company transaction where the doc type for CC X should be vendor Payment 'KZ' while the doc type for CC Y should be a customer reciept with doc type 'DZ'.
Although I am able to map the accounts in cross company code config I am not able to split the transaction of different company codes with different document types.
Is there any way we can do this in standard SAP?
Thanks in advance,
Nitish

Hi
As per your issue ...There are no possibilities to post in sap with different document types.
If you want you can post cross company code transactions with one document types
Regards
vamsi

Cross company transactions customization Help - Urgent...

Hi All,
Can anyone tell me where I have to do the customization for cross company transactions,
In the scenarios
1. for materials shipped to the customer of company code BBBB, by company code AAAA on behalf of company code BBBB or vice versa
2. For materials shipped to plant of company code BBBB from the plant of company code AAAA or vice versa.
I would appreciate it, if you can help with customization and configuration steps involved in cross company transactions.
Thanks in advance
Kumar

Hi Kumar,
With OBYA settings, you will be able to affect cross company code transactions through FI.
Ex. Maintenance Exp of co. code AAAA are paid by co. code BBBB. Now the affect will be as follows:
Books of AAAA:
Maintenance Exp A/c Dr and Cross Company code Clearing (say 'BBBB') A/c Cr
Books of BBBB:
Cross Company code Clearing (say 'AAAA') A/c Dr and Bank A/c Cr
The above affect will take place in books of both the company codes, when u post the document in any one set of books by mentioning the other company code as 'new company code'.
Hope this helps..

Error During T.code J1iex (Balance in Transaction Currency)

System not allowing to post excise invoice , and throwing error massage " Balance in Transaction currencey "

Hi
Please tell me what is your.
Group Currency ?
Company Code Currency ?
Documents Currency (Transaction Currency) ?
Please check your end and try to post the document again.
Warm Regards,
Sivakumar Sathiyamoorthy

Cross company transaction between different operating concerns

Dear Gurus
we have scenario for new implementation that we have to enable Cross company code transaction between different operating concerns. Stock movements and other inter company purchases etc
Please advise is this possible or not.

Dear Mohsin,
is it only for stock transactions??
Regards,
Raman

Cross Company Transaction and RFBUST10

Hello SAP Professionals,
I have a problem with a Cross-Company Code Transaction combined with Tax. In the case of cross-company code transactions, the whole tax amount is posted to and displayed in the first company code only. The taxes occurring in other company codes are ignored.
But I would like to transfer and to display the right Tax amount in another Company Code at the advance Return for Tax on Sales/Purchase (TA S_ALR_87012357). I’ve found the report RFBUST10 and the Customizing view TBUVTX. With this report it should be possible to do what I want.
When I execute it, the right amounts are posted to the other company code but it is just a 50/40 posting without any tax data. So the table BSET isn’t changing and because it’s the base for the advance Return for Tax on Sales/Purchase the Tax amounts are still incorrect there. It looks like he has a problem with postings where Tax Code A0/V0 (Input Tax / Output Tax = 0) is used. With other Tax code, where Tax > 0, he is doing it like expected.
Does anybody have experience with the RFBUST10? How can I use the RFBUST10 to transfer amounts posted with A0/V0? Is it possible somehow?
Thank you for your help.
Greetings Enrico

Hi Enrico,
I am afraid this is the standard behaviour of the system, we may not be able to do much in this regard.
Regards,
Ravi

Cross company transaction - STO

Hi all,
I want to make Inter company PO but I am not getting the Shipping Tab in item level. All Sales view is maintained in Material Master for both the Plant and Material. Could anybody help regarding the Settings of Shipping point to get Shipping tab while creating the PO.
If any Sales module setting if required please inform.
Already for one Plant it is getting, but same I have to maintain for another Plants.
At backend supply plant & receiveing Plant for Doc type is maintained and checking rule is also assinged.
I am getting error "Customer xxxxxx does not exist" while creating a cross company STO - PO".
regards,

have u dont the setting for shiping date for plants
do the setting for the plant
create a customer for a plant and assign in following
spro-- mm-purcpur ordset up sto
Define Shipping Data for Plants
ur issue will be solved
Message was edited by:
Umakant Bhangale

Cross-Company Transaction and Inter Company setting

Dear Support Team,
I am working a new Project , and there is a requirement of Cross company i,e , we have multiple company code & diff plants and we have a inter company transaction its a very new kind of scenario , sp pls me out by providing a usefull configuration and setting document so that I can able to do .
Thanks & Regards
MKS

Hi ,
All settings will remains same. only thing u have to do is in OBYA t code assign g/l account for inter company code clearence. and posting key will be 40 & 50.
Regards
Mahesh M J

Cross Company Transactions

Hi,
In our present client we have 5 company codes and there are intercompany transactions between them.
I have made relevant settings via T-code OBYA.
Pls adv me what are the closing activities for Intercompany transactions..Do we need to manually set off IC payable and Recv at the month end? Is there any process for this.
Thanks

The only thing i can think of is:
Make sure that Sum of Inter company balances is Zero.
I am not sure how you guys are handling the elimination entries for intercompany transactions - Do you enter it in a seperate ledger ? or a seperate co cd ? If so, make sure that all those entries are entered.
Hope it helps..
Thanks,
Nandita

HPCM Error(During the calculation cube i am getting the error)

Dear All,
I am working with HPCM 11.1.1.3. While deploying the calculation cube, i am getting the below error.
2010-01-12 20:06:50,828 [Thread-17] ERROR com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerator: error setting measures dimension member properties
com.hyperion.profitability.data.mdb.essbase.MDBException: Error setting member property share option to store_data for member: OP RV PAX UMRAH
     at com.hyperion.profitability.data.mdb.essbase.MDBMember.setShareOption(MDBMember.java:451)
     at com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerator.setMemberProperties(CubeGenerator.java:1434)
     at com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerator.traverseDimensionAndSetProperties(CubeGenerator.java:1142)
     at com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerator.createDimensionAndMembers(CubeGenerator.java:870)
     at com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerator.createOutline(CubeGenerator.java:402)
     at com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerator.deployCube(CubeGenerator.java:197)
     at com.hyperion.profitability.business.service.CubeDeployer.deployCube(CubeDeployer.java:60)
     at com.hyperion.profitability.business.service.ServiceFacade.deployCube(ServiceFacade.java:717)
     at com.hyperion.profitability.business.integration.ces.jobs.DeployCubeJob.start(DeployCubeJob.java:35)
     at com.hyperion.profitability.business.integration.ces.TaskHandler$AgentThread.run(TaskHandler.java:128)
Caused by: com.essbase.api.base.EssException: Cannot find member. Object not found.
     at com.essbase.api.metadata.EssCubeOutline.findMember(Unknown Source)
     at com.hyperion.profitability.data.mdb.essbase.MDBMember.setShareOption(MDBMember.java:429)
     ... 9 more
2010-01-12 20:06:50,828 [Thread-17] ERROR com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerator: building Dimension and hierarchy failed
com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerationException
     at com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerator.traverseDimensionAndSetProperties(CubeGenerator.java:1147)
     at com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerator.createDimensionAndMembers(CubeGenerator.java:870)
     at com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerator.createOutline(CubeGenerator.java:402)
     at com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerator.deployCube(CubeGenerator.java:197)
     at com.hyperion.profitability.business.service.CubeDeployer.deployCube(CubeDeployer.java:60)
     at com.hyperion.profitability.business.service.ServiceFacade.deployCube(ServiceFacade.java:717)
     at com.hyperion.profitability.business.integration.ces.jobs.DeployCubeJob.start(DeployCubeJob.java:35)
     at com.hyperion.profitability.business.integration.ces.TaskHandler$AgentThread.run(TaskHandler.java:128)
Caused by: com.hyperion.profitability.data.mdb.essbase.MDBException: Error setting member property share option to store_data for member: OP RV PAX UMRAH
     at com.hyperion.profitability.data.mdb.essbase.MDBMember.setShareOption(MDBMember.java:451)
     at com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerator.setMemberProperties(CubeGenerator.java:1434)
     at com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerator.traverseDimensionAndSetProperties(CubeGenerator.java:1142)
     ... 7 more
Caused by: com.essbase.api.base.EssException: Cannot find member. Object not found.
     at com.essbase.api.metadata.EssCubeOutline.findMember(Unknown Source)
     at com.hyperion.profitability.data.mdb.essbase.MDBMember.setShareOption(MDBMember.java:429)
     ... 9 more
2010-01-12 20:06:50,828 [Thread-17] ERROR com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerator: createOutline failed with CubeGenerationException
com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerationException
     at com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerator.createDimensionAndMembers(CubeGenerator.java:880)
     at com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerator.createOutline(CubeGenerator.java:402)
     at com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerator.deployCube(CubeGenerator.java:197)
     at com.hyperion.profitability.business.service.CubeDeployer.deployCube(CubeDeployer.java:60)
     at com.hyperion.profitability.business.service.ServiceFacade.deployCube(ServiceFacade.java:717)
     at com.hyperion.profitability.business.integration.ces.jobs.DeployCubeJob.start(DeployCubeJob.java:35)
     at com.hyperion.profitability.business.integration.ces.TaskHandler$AgentThread.run(TaskHandler.java:128)
Caused by: com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerationException
     at com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerator.traverseDimensionAndSetProperties(CubeGenerator.java:1147)
     at com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerator.createDimensionAndMembers(CubeGenerator.java:870)
     ... 6 more
Caused by: com.hyperion.profitability.data.mdb.essbase.MDBException: Error setting member property share option to store_data for member: OP RV PAX UMRAH
     at com.hyperion.profitability.data.mdb.essbase.MDBMember.setShareOption(MDBMember.java:451)
     at com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerator.setMemberProperties(CubeGenerator.java:1434)
     at com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerator.traverseDimensionAndSetProperties(CubeGenerator.java:1142)
     ... 7 more
Caused by: com.essbase.api.base.EssException: Cannot find member. Object not found.
     at com.essbase.api.metadata.EssCubeOutline.findMember(Unknown Source)
     at com.hyperion.profitability.data.mdb.essbase.MDBMember.setShareOption(MDBMember.java:429)
     ... 9 more
2010-01-12 20:06:50,828 [Thread-17] ERROR com.hyperion.profitability.business.service.CubeDeployer:
com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerationException
     at com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerator.createDimensionAndMembers(CubeGenerator.java:880)
     at com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerator.createOutline(CubeGenerator.java:402)
     at com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerator.deployCube(CubeGenerator.java:197)
     at com.hyperion.profitability.business.service.CubeDeployer.deployCube(CubeDeployer.java:60)
     at com.hyperion.profitability.business.service.ServiceFacade.deployCube(ServiceFacade.java:717)
     at com.hyperion.profitability.business.integration.ces.jobs.DeployCubeJob.start(DeployCubeJob.java:35)
     at com.hyperion.profitability.business.integration.ces.TaskHandler$AgentThread.run(TaskHandler.java:128)
Caused by: com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerationException
     at com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerator.traverseDimensionAndSetProperties(CubeGenerator.java:1147)
     at com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerator.createDimensionAndMembers(CubeGenerator.java:870)
     ... 6 more
Caused by: com.hyperion.profitability.data.mdb.essbase.MDBException: Error setting member property share option to store_data for member: OP RV PAX UMRAH
     at com.hyperion.profitability.data.mdb.essbase.MDBMember.setShareOption(MDBMember.java:451)
     at com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerator.setMemberProperties(CubeGenerator.java:1434)
     at com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerator.traverseDimensionAndSetProperties(CubeGenerator.java:1142)
     ... 7 more
Caused by: com.essbase.api.base.EssException: Cannot find member. Object not found.
     at com.essbase.api.metadata.EssCubeOutline.findMember(Unknown Source)
     at com.hyperion.profitability.data.mdb.essbase.MDBMember.setShareOption(MDBMember.java:429)
     ... 9 more
2010-01-12 20:06:50,828 [Thread-17] ERROR com.hyperion.profitability.business.integration.ces.jobs.DeployCubeJob: Error deploying cubes
com.hyperion.profitability.business.service.ServiceException: com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerationException
     at com.hyperion.profitability.business.service.CubeDeployer.deployCube(CubeDeployer.java:70)
     at com.hyperion.profitability.business.service.ServiceFacade.deployCube(ServiceFacade.java:717)
     at com.hyperion.profitability.business.integration.ces.jobs.DeployCubeJob.start(DeployCubeJob.java:35)
     at com.hyperion.profitability.business.integration.ces.TaskHandler$AgentThread.run(TaskHandler.java:128)
Caused by: com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerationException
     at com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerator.createDimensionAndMembers(CubeGenerator.java:880)
     at com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerator.createOutline(CubeGenerator.java:402)
     at com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerator.deployCube(CubeGenerator.java:197)
     at com.hyperion.profitability.business.service.CubeDeployer.deployCube(CubeDeployer.java:60)
     ... 3 more
Caused by: com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerationException
     at com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerator.traverseDimensionAndSetProperties(CubeGenerator.java:1147)
     at com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerator.createDimensionAndMembers(CubeGenerator.java:870)
     ... 6 more
Caused by: com.hyperion.profitability.data.mdb.essbase.MDBException: Error setting member property share option to store_data for member: OP RV PAX UMRAH
     at com.hyperion.profitability.data.mdb.essbase.MDBMember.setShareOption(MDBMember.java:451)
     at com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerator.setMemberProperties(CubeGenerator.java:1434)
     at com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerator.traverseDimensionAndSetProperties(CubeGenerator.java:1142)
     ... 7 more
Caused by: com.essbase.api.base.EssException: Cannot find member. Object not found.
     at com.essbase.api.metadata.EssCubeOutline.findMember(Unknown Source)
     at com.hyperion.profitability.data.mdb.essbase.MDBMember.setShareOption(MDBMember.java:429)
     ... 9 more
Please guide me in this situation.
Thanks,
Lakshmi

Hi Can anybody please look into this .We are getting below error while deploying HPCM application in Essbase. We made changes in registry files still we are facing the same error.
2011-01-11 20:13:00,303 [Thread-24] WARN com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerator: Can't close outline
com.essbase.api.base.EssException: Cannot close cube outline. Essbase Error(1290002): Network Error [10061]: Unable To Connect To [PC105728.cts.com:32778]. The client timed out waiting to connect to the Essbase Server using TCP/IP. Make sure that the client machine has sufficient number of ports available.
     at com.essbase.server.framework.EssOrbPluginDirect.ex_olap(Unknown Source)
     at com.essbase.server.framework.EssOlapMetaDataService.ex_olap(Unknown Source)
     at com.essbase.server.framework.EssOlapMetaDataService.closeOutline(Unknown Source)
     at com.essbase.server.framework.EssOtlConnectionContext.close(Unknown Source)
     at com.essbase.server.framework.EssOrbPluginDirect.closeOutline(Unknown Source)
     at com.essbase.api.session.EssOrbPlugin._invokeOutlineMethod(Unknown Source)
     at com.essbase.api.session.EssOrbPlugin._invokeMethod2(Unknown Source)
     at com.essbase.api.session.EssOrbPlugin._invokeMethod(Unknown Source)
     at com.essbase.server.framework.EssOrbPluginDirect._invokeProtected(Unknown Source)
     at com.essbase.api.session.EssOrbPluginEmbedded.invokeMethod(Unknown Source)
     at com.essbase.api.session.EssOrbPluginEmbedded.invokeMethod(Unknown Source)
     at com.essbase.api.session.EssOrbPlugin.closeOutline(Unknown Source)
     at com.essbase.api.metadata.EssCubeOutline.close(Unknown Source)
     at com.essbase.api.metadata.EssCubeOutline.close(Unknown Source)
     at com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerator.closeOutline(CubeGenerator.java:449)
     at com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerator.createOutline(CubeGenerator.java:428)
     at com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerator.deployCube(CubeGenerator.java:202)
     at com.hyperion.profitability.business.service.CubeDeployer.deployCube(CubeDeployer.java:60)
     at com.hyperion.profitability.business.service.ServiceFacade.deployCube(ServiceFacade.java:717)
     at com.hyperion.profitability.business.integration.ces.jobs.DeployCubeJob.start(DeployCubeJob.java:35)
     at com.hyperion.profitability.business.integration.ces.TaskHandler$AgentThread.run(TaskHandler.java:128)
2011-01-11 20:13:00,303 [Thread-24] ERROR com.hyperion.profitability.business.service.CubeDeployer:
com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerationException
     at com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerator.traverseDimensionAndSetProperties(CubeGenerator.java:1147)
     at com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerator.createPOVDimensionAndMembers(CubeGenerator.java:593)
     at com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerator.createOutline(CubeGenerator.java:392)
     at com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerator.deployCube(CubeGenerator.java:202)
     at com.hyperion.profitability.business.service.CubeDeployer.deployCube(CubeDeployer.java:60)
     at com.hyperion.profitability.business.service.ServiceFacade.deployCube(ServiceFacade.java:717)
     at com.hyperion.profitability.business.integration.ces.jobs.DeployCubeJob.start(DeployCubeJob.java:35)
     at com.hyperion.profitability.business.integration.ces.TaskHandler$AgentThread.run(TaskHandler.java:128)
Caused by: com.hyperion.profitability.data.mdb.essbase.MDBException: Error setting member property share option to store_data for member: November
     at com.hyperion.profitability.data.mdb.essbase.MDBMember.setShareOption(MDBMember.java:451)
     at com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerator.setMemberProperties(CubeGenerator.java:1434)
     at com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerator.traverseDimensionMemberAndSetProperties(CubeGenerator.java:1298)
     at com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerator.traverseDimensionAndSetProperties(CubeGenerator.java:1143)
     ... 7 more
Caused by: com.essbase.api.base.EssException: Cannot set member information. Essbase Error(1290002): Network Error [10061]: Unable To Connect To [PC105728.cts.com:32778]. The client timed out waiting to connect to the Essbase Server using TCP/IP. Make sure that the client machine has sufficient number of ports available.
     at com.essbase.server.framework.EssOrbPluginDirect.ex_olap(Unknown Source)
     at com.essbase.server.framework.EssOlapMetaDataService.ex_olap(Unknown Source)
     at com.essbase.server.framework.EssOlapMetaDataService.essOtlSetMemberInfo(Unknown Source)
     at com.essbase.server.framework.EssOrbPluginDirect.essOtlSetMemberInfo(Unknown Source)
     at com.essbase.api.session.EssOrbPlugin._invokeOutlineMethod(Unknown Source)
     at com.essbase.api.session.EssOrbPlugin._invokeMethod2(Unknown Source)
     at com.essbase.api.session.EssOrbPlugin._invokeMethod(Unknown Source)
     at com.essbase.server.framework.EssOrbPluginDirect._invokeProtected(Unknown Source)
     at com.essbase.api.session.EssOrbPluginEmbedded.invokeMethod(Unknown Source)
     at com.essbase.api.session.EssOrbPluginEmbedded.invokeMethod(Unknown Source)
     at com.essbase.api.session.EssOrbPlugin.essOtlSetMemberInfo(Unknown Source)
     at com.essbase.api.metadata.EssMember.updatePropertyValues(Unknown Source)
     at com.hyperion.profitability.data.mdb.essbase.MDBMember.setShareOption(MDBMember.java:449)
     ... 10 more
2011-01-11 20:13:00,303 [Thread-24] ERROR com.hyperion.profitability.business.integration.ces.jobs.DeployCubeJob: Error deploying cubes
com.hyperion.profitability.business.service.ServiceException: com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerationException
     at com.hyperion.profitability.business.service.CubeDeployer.deployCube(CubeDeployer.java:70)
     at com.hyperion.profitability.business.service.ServiceFacade.deployCube(ServiceFacade.java:717)
     at com.hyperion.profitability.business.integration.ces.jobs.DeployCubeJob.start(DeployCubeJob.java:35)
     at com.hyperion.profitability.business.integration.ces.TaskHandler$AgentThread.run(TaskHandler.java:128)
Caused by: com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerationException
     at com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerator.traverseDimensionAndSetProperties(CubeGenerator.java:1147)
     at com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerator.createPOVDimensionAndMembers(CubeGenerator.java:593)
     at com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerator.createOutline(CubeGenerator.java:392)
     at com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerator.deployCube(CubeGenerator.java:202)
     at com.hyperion.profitability.business.service.CubeDeployer.deployCube(CubeDeployer.java:60)
     ... 3 more
Caused by: com.hyperion.profitability.data.mdb.essbase.MDBException: Error setting member property share option to store_data for member: November
     at com.hyperion.profitability.data.mdb.essbase.MDBMember.setShareOption(MDBMember.java:451)
     at com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerator.setMemberProperties(CubeGenerator.java:1434)
     at com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerator.traverseDimensionMemberAndSetProperties(CubeGenerator.java:1298)
     at com.hyperion.profitability.business.mdb.deployment.cubegeneration.CubeGenerator.traverseDimensionAndSetProperties(CubeGenerator.java:1143)
     ... 7 more
Caused by: com.essbase.api.base.EssException: Cannot set member information. Essbase Error(1290002): Network Error [10061]: Unable To Connect To [PC105728.cts.com:32778]. The client timed out waiting to connect to the Essbase Server using TCP/IP. Make sure that the client machine has sufficient number of ports available.
     at com.essbase.server.framework.EssOrbPluginDirect.ex_olap(Unknown Source)
     at com.essbase.server.framework.EssOlapMetaDataService.ex_olap(Unknown Source)
     at com.essbase.server.framework.EssOlapMetaDataService.essOtlSetMemberInfo(Unknown Source)
     at com.essbase.server.framework.EssOrbPluginDirect.essOtlSetMemberInfo(Unknown Source)
     at com.essbase.api.session.EssOrbPlugin._invokeOutlineMethod(Unknown Source)
     at com.essbase.api.session.EssOrbPlugin._invokeMethod2(Unknown Source)
     at com.essbase.api.session.EssOrbPlugin._invokeMethod(Unknown Source)
     at com.essbase.server.framework.EssOrbPluginDirect._invokeProtected(Unknown Source)
     at com.essbase.api.session.EssOrbPluginEmbedded.invokeMethod(Unknown Source)
     at com.essbase.api.session.EssOrbPluginEmbedded.invokeMethod(Unknown Source)
     at com.essbase.api.session.EssOrbPlugin.essOtlSetMemberInfo(Unknown Source)
     at com.essbase.api.metadata.EssMember.updatePropertyValues(Unknown Source)
     at com.hyperion.profitability.data.mdb.essbase.MDBMember.setShareOption(MDBMember.java:449)
     ... 10 more

Cost Error During T code CO11

HI..
During saving a confirmation in CO11 , i m getting costing errors as
1. Substitution was deactivated for account determination.
2. Company code clearing account for 11111 2BP01 is not defined
3. Posting key is not defined.
4. No account type has been specified for posting key
BP01 is my controlling area.
what is setting i have to do, to come out of this ??
Thnks in advance

Dear,
Please check OSS NOte 201820. I hope you are missing customization
Also check T.code OB41...to see whether the PK is there.
Check what company code assigned .
check these
BAPI_SALESORDER_CREATEFROMDAT2 configuration
Also check if the given company code exist in the system at path below.
SPRO --> Enterprise Structure --> Definition --> Financial Accounting --> Edit, Copy, Delete, Check Company Code --> On the popup screen select " Edit Company Code Data", then see if your company code 'XXXX' exist.
Regards,
R.Brahmankar

Urgent pls ! Error during Container code generation using weblogic.ejbc

HI all,
Iam using weblogic6.1 and EJB 2.0. I have to communicate session and entity ejb's and iam using local interfaces for entity beans and access the entity beans thru session ejb's. After creating my programs and jar files, when i use java weblogic.ejbc code.jar Containercode.jar, i get the following error....
--------- Error -------------
C:\Sathish\Ejb\wl6.1\LocalInterfaces\Code\ejbcgen\CodeBean_tvm2r0_ELOImpl.java:34
0: cannot resolve symbol
symbol : constructor EJBException (java.lang.String,java.lang.Exception)
location: class javax.ejb.EJBException
throw new javax.ejb.EJBException("Unexpected exception in " +
^
1 errors
Exec failed .. exiting
Can anyone say why this error is occuring......
regards
sathish

In J2EE 1.3, EJBException added a third constructor of the form:
EJBException(java.lang.String, java.lang.Exception)
WebLogic contains a file called j2ee12.jar in the lib directory that when placed in front of the classpath, disables J2EE 1.3 features and replaces them with J2EE 1.2. In J2EE 1.2 this constructor did not exist.
So in order to compile using J2EE 1.3 features, you must make sure that j2ee12.jar is not in your classpath.

Error during installation code 30174-4

Good day
I have this issue.
While we are trying to install Office 365, this error message shows up. We have tried eveything: run some FIX IT from Microsoft, check the LAN, firewall, antivirus and proxy and it's still happening.
My customer installs Windows from scratch to avoid any other possible issue and it's still happening.
We have successfully install Office in another computers in the same network with NO ISSUE at all.
What could it be the solution for this?
Regards.
José

Hi,
30174-4 is a typical error code for Office 365 installation if the antivirus or malware software or firewall is interfering with the Office install.
Not sure what exactly do you mean by "check the LAN, firewall, antivirus and proxy", but to fix this error, it is recommended to temporarily
turn off antivirus software/firewall/proxy settings.
The issue could also be caused by the confused network address, you might want to try in another network environment and see if it works.
In addition, please make sure that all the URLs and IP address used by Office 365 users haven't been blocked. See:
http://technet.microsoft.com/en-us/library/hh373144.aspx
Regards,
Ethan Hua
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.

ERROR DURING T.CODE F-53 ( cross company transaction error)

Similar Messages

Maybe you are looking for