Internal posting

We would like to change our organization structure and make divisional organization in way to separate between production department, sales department and corporate.
Now we have more than 100 cost centers and about 30 profit centers.
Main problem is that we need to split costs and revenues by divisions and we need to know if it is possible to make some kind of internal posting ( or internal billing ) between divisions without any impact on accounting in way that we can make independent reports by divisions.
Best regards,
B&A

Hi,
You can make indeed internal CO posting via KB11N transaction.
Regards,
Eli

Similar Messages

E-Recruiting: Internal Posting Application (Internal Candidate)

Module:
e-Recruiting: Internal Posting Application (Internal Candidate)
Case/scenario:
Candidate submits internal posting application via Customised Internal Posting Application (PDF) form in Portal.
Question:
How to attach/create the Customised Internal Posting Application (PDF) form in the candidate's attachment table HRP5134.
Please provide SAP Standard/sample program/references for the followings:
1) Creating Data in HRP5134 (Attachments) - Attach Internal Posting Application form in the candidate's (Object NA) attachment table.
2) Creating Data in HRP5135 (Manual Activities) - Activities 1015 (Acknowledge Internal Candidate) for Object ND.
Regards,
Bart
012-2547375

Hi,
can you tell us the technology which you are using?
If it is BSP the coding decides the channel used for the seach based on th is_employee information. Here a wrong system behaviour could be caused by missing authorization on the employee object (P). In this case the application might not be able to read the P object which would let the internal candidate appear as external one. The application would change to the external application coding and show the external publication.
If it is Web Dynpro it points to a wrong application linked. The web dynpro application calls a certain inbound plug in the web dynpro component. If the wrong application is used the wrong plug would be supplied and the application could switch to the external publication. Same would happen if you entered the wrong plug in the in the startpage configuration.
Another thing which comes to my mind rading that it only effects some employees. Have you checked field IS_INACTIVE in HRP5102 for these employees?
Kind Regards
Roman

Create entry in Internal Posting table COSS

Hi All,
I want to create an entry in table COSS..
Please help me...
Thnx
Rohit

You can enter data Programatically but it is not a correct approach.
Create a Table maintenance Generator to for table COSS to make an Entry.
follow below steps
1) go to se11 check table maintanance check box under
attributes tab
2) utilities-table maintanance Generator->
create function group and assign it under
function group input box.
also assign authorization group default &NC& .
3)
select standard recording routine radio in table
table mainitainence generator to move table
contents to quality and production by assigning
it to request.
4) select maintaience type as single step.
5) maintainence screen as system generated numbers
this dialog box appears when you click on create
button
6) save and activate table
OR.
Check Tcode for the COSS table and Use BDC.
Regards,
Gurpreet

Posting a particular Ledger using BAPI_ACC_DOCUMENT_POST

Is it possible to post to a specific ledger using the BAPI_ACC_DOCUMENT_POST.
Currently we use a BDC on FB01L and would like to convert this into a BAPI, Can this be done ?

Hi,
You can try with Posting Interface, please try with the following posting interface.
POSTING_INTERFACE_CLEARING     Post with clearing (FB05) using internal posting interface
POSTING_INTERFACE_DOCUMENT     Post document using the internal posting interface
POSTING_INTERFACE_END
POSTING_INTERFACE_RESET_CLEAR Reset clearing via posting interface
POSTING_INTERFACE_REVERSE_DOC Cancel document via posting interface
POSTING_INTERFACE_START        Initial information for internal accounting interface
Regards
Pugazhenthi.P

Posting_interface_reverse_doc call transcation FB08. Is there also a posting interface for call transaction F.80

Hello,
With internal posting interface:
posting_interface_reverse_doc
Reverse posting can be made by call transaction FB08 (also batch input)
My quesition ist:
Do we have a posting interface where I can make reversal postings by call transaction F.80 mass reversal.
Thank you for you valueable help and answer.
all the best Erwin

Hi:
You yourself are telling issue faced , you are saying that you have checked in OBC4 and OB41 the business area is has been set as required entry. When this has been set as required entry the field status group of GL Account 14470000 then it is obvious thing that you will get the error Field Bus. Area is a required field for G/L account 2100 14470000 in VF02. Normally Business area is coped to billing document from material master data , you do not need to enter in manually in GL account line item. If you want avoid this error then set Business area as optional in relevant field status group of GL account and posting key used. This will surely resolved your issue.
Regards

Report HRALXSYNC error in Internal candidate creation

Hi All,
I am running HRALXSYNC report for an employee and i am getting the error(Red icon) in the Internal Candidate Column. When I debugged it i found out that there was no NA created for the CP.. so when i tried to repair it then also the error was existing..
Can anybody please let me know the reason why the error is coming..Also please let me know where will i be able to see the error...
Thanks and Regards,
Salish

Hello Salish,
the integration of hr core with e-recruiting is a quite complex processing. The integration links into the HR-Business Partner integration and runs basically synchronous.
When certain things are maintained in the personal administration, this triggers an internal post processing (in fact it is trigered for every single infotype record created). This post processing consists of BAdI implementations and some T77S0 switches. When the necessary configuration is done it creates a central person for the employee, a business partner and a candidate for e-recruiting. How this works in detail is unfortunately very difficult to investigate, especially as w/ EhP4 this integration using HRALXSYNC is also used in the standalone scenario where the new infotypes 558* are accessed instead of the standard PA ones. For an example the central person is created in every case, the business partner only if an infotype 6 is maintained. The infotype 6 restriction can be bypassed again with special country grouping configuration and matching t005 ebtries but no business partner will be created at all if the hiring is in the future. A huge part of the coding is based on sap notes and some things do not match the documentation, so there are t77s0 switches whichs reading is commented in the coding followd by a hard coded SWITCH = X. statement.
Where does HRALXSYNC fits into this? In the common case you have a HR system which has already been running for some time when e-recruiting is rolled out. So the integration to e-rec could not be active when most of the employee data, usually there are also no business partners as they were not needed so far. If you activate the integration settings you would have to create a change for every single employee to trigger the synchronous processing. As you can't just for fun change HR data for thousands of employees there is HRALXSYNC. This report basically forces the processing for the selected employees - more or less by calling the BAdIs. Furthermore it starts the processing for employees hired in future when their entry date is reached that's why you have to plan it to run daily after the initial run.
Kind Regards
Roman

Job Posting for CMS Business Lead

Please contact [email protected] for more information or to apply. Full posting is below.
Job Title: Online Business Application Manager
Location: Reston, VA, London, UK, or Olso, Norway
Contact Email: [email protected]
TANDBERG is a leading global provider of telepresence, high-definition videoconferencing and mobile video products and services with dual headquarters in New York and Norway. TANDBERG designs, develops and markets systems and software for video, voice and data. The company provides sales, support and value-added services in more than 90 countries worldwide. TANDBERG is publicly traded on the Oslo Stock Exchange under the ticker TAA.OL. Please visit www.tandberg.com for more information.
Job Summary
• The role is part of the online marketing team, reporting to the Director of Online Marketing, with a dotted line responsibility to the Global Channels Director.
• Responsible for the strategic planning, design, implementation, and ongoing development of TANDBERG's global content management system (CMS) and the websites and portals it supports.
• From a project management perspective, work with TANDBERG’s online and global channels team, internal IT department and external vendors to keep ongoing CMS development on track, within budget, and adhering to best practices for governance, scalability and usability.
• Work with multiple departments globally, including IT, marketing, services, operations, support, logistics, training, and channel sales to integrate business requirements of all stakeholders into CMS development.
Essential Duties & Key Responsibilities
• Facilitate requirements definition, define development plan priorities and phases, and identify timeline and key roles and responsibilities for CMS and partner portal, in collaboration with multiple business owners.
• Identify and secure implementation resources and appropriate vendors required for ongoing CMS development and integration of CMS with existing and new business applications
• Organize project team meetings, guide and report on progress of internal and 3rd party teams
• Build templates, train superusers and set best practices for monthly landing pages on TANDBERG’s partner portal with global channels content and promotions. Ensure global partners have personalized content pages for all portal users. Support global partners with portal usage and account management.
• Proactively make recommendations for improvements in functionality and design, based on analysis and reporting of usage and adoption of the CMS and its portals.
• Identify and accelerate areas of concern to business owners.
Knowledge (The knowledge level is used as an approximation of years only and does not rule out individuals with more or less experience/knowledge. )
~10 years
Skills & Abilities
• Strong project management skills, including cross-departmental and cross-cultural experience.
• Ability to rapidly understand business functions and the technology applications that support them.
• Knowledge and interest in web marketing techniques, such as search engine optimization, template-building, web analytics/reporting.
• Solid analytical and problem solving skills.
• Excellent communication skills.
• Strong relationship skills and the ability to work in a team environment.
• Flexible and ability to multi-task in a fast-paced environment.
• Training abilities.
• Vendor management
• Customer focused.
• Understanding of B2B ecommerce a plus.
• Marketing experience a plus.
Computer Abilities
• Experience with Web-based content management systems
• Experience with Project Management software
• Expert with Microsoft Office Suite
Education & Certifications (list any certifications, licenses, or accreditation required):
BA/BS degree in marketing, business or information technology
MS degree desired
Training with Content Management Systems as plus
Working Conditions Normal Office Environment
Physical Demands
(list any specific demands):
Physical Activities: N/A
Lifting Requirements: N/A
Vision Requirements: N/A
TANDBERG is an equal opportunity/affirmative action employer (M/F/V/D). We support diversity in our workforce. Please note those individuals submitting resumes online or by mailing a resume are not considered an applicant for employment until a signed employment application form is completed, usually at the time of interview
TANDBERG reserves the right at its sole discretion to change, modify, suspend, or terminate any of the guidelines, elements, or the design of this job description at any time.

Did you check the profile option - IRC: Internal Posting Days
From the Implementation guide - http://docs.oracle.com/cd/E18727_01/doc.121/e13518/T24319T440324.htm
Set posting days to define the number of days for internal job postings
If you want to make the job details available to your employees first, then set the IRC: Internal Posting Days profile option. You specify the number of days that the application posts an advertisement internally before posting the advertisement on the external site.
Cheers,
Vignesh

Posting of Derived Business transactions

Dear SAP Gurus
Recently I had a requirement wherein the DBT was to be posted to SL. I found that DBT posting is not possible to SL and the system gave me an error message that the "amount is not available in payment currency"
The question is when the system allows a normal flow to be posted to SL in payment currency why not in case of Derived Business Transaction. Is there a workaround available
Any help would be appreciated.
Regards
Virendra Malik

Hi
You have rightly said that DBT is meant for internal posting and ideally must be posted to a GL only. However I have this special requirement when I want to do the posting through DBT for update type DBT_E002 (Translation of Negative Purchase Value). In this case I do not want to do the SL posting of foreign currency repayment which is represented by the the main flow (update type MM1130-). This main flow update type has the net amount of two transactions DBT_E002 (Translation of Negative Purchase Value) and DBT_B006 (Forex Gain (planned outflow)). I want the SL posting to be done of the amount being shown in DBT_E002 and Gl posting for the amount being shown in DBT_B006.
Hope the above clarifies.
Regards
Virendra Malik

International Use under new User Agreement

As a member of the US military, I use my MacBook abroad extensively. I used it for entertainment and for study while deployed to counter-drug operations in South America, Presidential support in South America and the Caribbean, and combat operations in the middle east. Now, according to the new User Agreement that is popping up each time I try to purchase a new song from iTunes, I will no longer be able to use iTunes and it's associated content while outside of the US. Is this a joke? Not that I would expect Apple, with it's outward bias against US military personnel, to bend over backwards to help out, but is there any exception in this policy to protect continued use by deployed or internationally posted military personnel and their families? There's been a trend over the past couple of years of more folks I've been deployed with having Macs instead of PCs, but a policy push like this (to go along with the nightmare of trying to take an iPhone abroad, even to Canada) will drive the entire military community away from Apple products. Why would a military member buy a high-dollar Apple product if they know an inevitable move overseas will render their product unusable? If anybody knows of a work-around, I'd love to know.
Apple: heads up, it's only a matter of time before the military community will begin to speak up against this. Fix the policies that will keep us away, please.

I never suggested you were stupid.
I'm not looking for any more responses implying that I'm stupid or that this is somehow the fault of the tax-paying public.
It is the fault of the music industry and arcane copyright laws not being updated to account for the internet and a global economy.
The fact that other organizations are also working under ill-conceived policies is not an excuse.
It's not ill-concieved policies.
It's contract law and international copyright law.
International copyright laws need to be changed.
Apple (and any other corporation) can only legally sell products for which they have a contract to sell.
Music contracts are not granted to sell a song everywhere, world-wide. They must be negotiated separately for each country, depending on the copyright laws for those countries.
EMI may have the copyright for an album in the U.S., but the copyright may be owned by a different company in Brazil, a different company in Spain and a different comapny in Germany. Even if a company holds the copyright for every country, it still must be negotiated separately for each country.
If companies were to sell copyright materials in countries in which they do not have a contract, they would be in breach of those copyright laws.
And thank you for the hint that posts that may be negative in nature will be deleted
It's has nothing to do with it being a negative post.
The fact that a post is directly against the terms of use or may contain info which may be illegal is enough to get a post deleted and rightfully so.
Kinda like RIPping a DVD to your computer +for your own personal use+ is illegal according to the DMCA, but many people comsider there is nothing wrong with it.
The fact that it is illegal, makes it against the terms of use of these forums.
Good job! I look forward to this topic being deleted.
I suggest that since Apple states it is against the terms of use for the iTunes store, that you simply do not use iTunes while out of the country.
Sorry for trying to help you out.

Line item description

Hi Experts,
I need to fetch the cost element or account number or ??? line item <b>description</b> for the posting without purchase order.
The description has to come based on the document type (BLART).
I have done for SA and KR document type (SA For GL Internal posting and KR for Vendor invoice) by fetching the right field from the table.
My problem is if i have more document type other than SA or KR, my description will not apper in my report output. The major problem is tat i dont have function guy or any functional input. My question is for a cost center will there be any other document type other than SA and KR document type. I found in a table t003t there are lot of document type, if all this comes in my report later point the description will not be listed. How to proceed with this?
Regards,
Senthil

Hi,
You can write the Select statement outside your loop statement as below.
1) Declare an internal table as below
   data : begin of i_skat occurs 0,
             spras like skat-spras,
             ktopl like skat-ktopl,
             saknr like skat-saknr,
             txt20 like skat-txt20,
          end of i_skat.
2)if not itab[] is initial.
   select spras
          ktopl
          saknr
          txt20
     into table i_skat
     from skat
     for all entries in itab
     where spras eq sy-langu and
           ktopl = itab-ktopl and
           saknr = itab-hkont.
   if sy-subrc = 0.
      sort i_skat by saknr.
   endif.
endif.
3) The place you have written select statement there you write Read statent as below.
   read table i_skat with key spras = sy-langu
                              ktopl = itab-ktopl
                              saknr = itab-saknr
                              binary search.
   if sy-subrc = 0.
      itab-txt20 = i_skat-txt20.
   endif.

Foreign JMS and XA

Hi everybody,
          Is anybody successfully using remote IBM MQseries 5.3 server as
          Foreign JMS in WLS 8.1sp2?
          We're observing some strange behavior in this case. Here is our setup:
          WLS and IBM MQ server deployed on separate boxes.
          WLS version 8.1sp2 running on Windows 2000/Intel
          IBM MQ version 5.3 running on Solaris/SPARC
          We're using "WebSphere MQ classes for Java, version 5.303 - j5303-L030225"
          and "WebSphere MQ Extended Transactional Client Feature, version 5.300 -
          j5303-L030122"
          MQ files added in WLS POST_CLASSPATH variable in WLS starup script.
          Foreign JMS server configured in WLS via fscontext JNDI.
          MDB bean deployed with Transaction attribute "Required".
          Everything seems to work fine, if we're posting message to MQ queue MDB
          receives it and process successfully (just print message content to the
          console for now).
          Problem: In WLS console, under Server->Monitoring->JTA->Monitor inflight
          transactions we can constantly see one transaction enlisted for our MDB
          bean with following details:
          =====================================================
          Transaction ID: BEA1-00DFC5EB4B7B7F28EDB9
          Coordinator: mydomain+myserver
          Name: JMSMessagePoller.xxx.xxx.MyMessageProcessorMdb
          Status: Active
          Seconds Active: 17
          Resources:
          weblogic.ejb20.JMSConnectionPoller.xxx.xxx.MyMessageProcessorMdb=started
          Properties
          (key=value):
          weblogic.transaction.name=JMSMessagePoller.xxx.xxx.MyMessageProcessorMdb
          =====================================================
          This transaction seems to be Active for 30 seconds and then rolled back
          (no error messages on WLS console displayed).On JTA statistics page in
          WLS console "Total Rolled Back" counter keeps increneting with every
          rollback.
          Does anybody observerd similar problem? May be it's normal behaviour but
          I'm kind of worrying about those transactions and constant rollback. I'd
          appreciate any feedback.
          Sincerely,
          Dmitri Maximovich


Hi Dmitri,
          The shutdown "suspend" failure has nothing to do with transactions
          or JMS. It looks like the failure is due to a
          java.util.ConcurrentModificationException during undeployment
          which indicates a bug in WL - something is not getting
          synchronized that should be.
          As for MQ, their new extended client supports remote XA, which I think
          is the reason for the product in the first place. Even so, I
          still recommend testing to make sure that its messages
          participate in transactions. (Actually, I recommend such testing
          for any transactional app, including those built on WL JMS.)
          Tom
          Dmitri Maximovich wrote:
          > Hi Tom,
          >
          > Thanks for info, that's a relief. Unfortunately there is no hints in WLS
          > documentation that it's normal, that's why we were worried about it.
          >
          > Now there is one more issue, which I believe is related. You see with
          > those 'in-flight' transactions graceful shutdown of WLS doesn't quite
          > work. There is suspicious exception thrown and after that WLS is still
          > running in some state but console is not available anymore. Please see
          > console messages attached (sorry for long post). at the time of shutdown
          > there is no messages in the queue(s) so as far as I can tell those
          > 'pending transactions' mentioned is those from foreign JMS wrappers.
          >
          > I'd appreciate any comments on that. We have case opened with BEA about
          > this but so far they cannot reproduce it in their lab. That's why I
          > start wondering if we're doing something wrong here, like using remote
          > MQ server for example, may be you not supposed to (I remember there was
          > an issue before with IBM MQ that XA support required binding mode, I was
          > kind of hope that it's not the case anymore)?
          >
          > <Mar 3, 2004 1:47:56 PM EST> <Notice> <WebLogicServer> <BEA-000365>
          > <Server state changed to SUSPENDING>
          > <Mar 3, 2004 1:47:56 PM EST> <Info> <Deployer> <BEA-149236> <Preparing
          > to suspend.>
          > <Mar 3, 2004 1:47:56 PM EST> <Info> <Deployer> <BEA-149237> <Ready to
          > suspend.>
          > <Mar 3, 2004 1:47:56 PM EST> <Info> <WebService> <BEA-220028> <Web
          > Service reliable agents are suspended.>
          > <Mar 3, 2004 1:47:56 PM EST> <Notice> <JTA> <BEA-110476> <The server has
          > detected pending transactions during graceful shutdown. The server will
          > wait for the pending transactions to complete before suspending the RMI
          > service. A force shutdown command can be issued to shutdown the server
          > immediately.>
          > <Mar 3, 2004 1:48:26 PM EST> <Info> <Management> <BEA-141080> <A request
          > has been received to force shut down of the server.>
          > <Mar 3, 2004 1:48:26 PM EST> <Alert> <WebLogicServer> <BEA-000228> <The
          > disabling of server logins has been requested by <WLS Kernel>>
          > <Mar 3, 2004 1:48:26 PM EST> <Alert> <WebLogicServer> <BEA-000229>
          > <Server logins have been disabled.>
          > <Mar 3, 2004 1:48:26 PM EST> <Info> <WebService> <BEA-220028> <Web
          > Service reliable agents are suspended.>
          > <Mar 3, 2004 1:48:26 PM EST> <Info> <EJB> <BEA-010084> <The
          > message-driven beans are being suspended. This may take a minute or two.>
          > <Mar 3, 2004 1:48:32 PM EST> <Info> <EJB> <BEA-010085> <The
          > message-driven beans have all been suspended.>
          > <Mar 3, 2004 1:48:32 PM EST> <Info> <EJB> <BEA-010084> <The
          > message-driven beans are being suspended. This may take a minute or two.>
          > <Mar 3, 2004 1:48:32 PM EST> <Info> <EJB> <BEA-010085> <The
          > message-driven beans have all been suspended.>
          > [MessageDrivenBeanPoolInfoImpl] : Couldn't unregister MBean
          > javax.management.InstanceNotFoundException:
          > mydomain:ApplicationRuntime=myserver_otis-dasl-ejb,EJBComponentRuntime=myserver_otis-dasl-ejb_otis-dasl-ejb.jar,Location=myserver,Name=myserver_otis-dasl-ejb_otis-dasl-ejb.jar_com.cibcwm.go.otis.dasl.submission.DASLSubmissionMdb_wls.mqs.dasl.dev.adp.reply3,ServerRuntime=myserver,Type=EJBTransactionRuntime
          >
          > at
          > com.sun.management.jmx.MBeanServerImpl.getMBean(MBeanServerImpl.java:1680)
          > at
          > com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1524)
          > at
          > weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:947)
          >
          > at
          > weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:908)
          >
          > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:946)
          > at
          > weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
          >
          > at
          > weblogic.management.runtime.EJBTransactionRuntimeMBean_Stub.preDeregister(EJBTransactionRuntimeMBean_Stub.java:433)
          >
          > at
          > weblogic.management.internal.MBeanHomeImpl.internalDeleteMBean(MBeanHomeImpl.java:996)
          >
          > at
          > weblogic.management.internal.MBeanHomeImpl.privateDeleteMBean(MBeanHomeImpl.java:982)
          >
          > at
          > weblogic.management.internal.MBeanHomeImpl.access$000(MBeanHomeImpl.java:74)
          >
          > at
          > weblogic.management.internal.MBeanHomeImpl$2.run(MBeanHomeImpl.java:948)
          > at
          > weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
          >
          > at
          > weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
          > at
          > weblogic.management.internal.MBeanHomeImpl.deleteMBeanWithKernelID(MBeanHomeImpl.java:944)
          >
          > at
          > weblogic.management.internal.MBeanHomeImpl.deleteMBean(MBeanHomeImpl.java:939)
          >
          > at
          > weblogic.management.internal.MBeanHomeImpl.deleteMBean(MBeanHomeImpl.java:933)
          >
          > at
          > weblogic.management.runtime.RuntimeMBeanDelegate.unregister(RuntimeMBeanDelegate.java:140)
          >
          > at
          > weblogic.ejb20.monitoring.EJBRuntimeMBeanImpl.unregisterDependents(EJBRuntimeMBeanImpl.java:58)
          >
          > at
          > weblogic.ejb20.monitoring.MessageDrivenEJBRuntimeMBeanImpl.unregisterDependents(MessageDrivenEJBRuntimeMBeanImpl.java:50)
          >
          > at
          > weblogic.ejb20.deployer.MessageDrivenBeanPoolInfoImpl.unInitPool(MessageDrivenBeanPoolInfoImpl.java:208)
          >
          > at
          > weblogic.ejb20.deployer.MessageDrivenBeanPoolInfoImpl.onUndeploy(MessageDrivenBeanPoolInfoImpl.java:121)
          >
          > at
          > weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.onUndeploy(MessageDrivenBeanInfoImpl.java:628)
          >
          > at weblogic.ejb20.internal.BaseEJBHome.undeploy(BaseEJBHome.java:203)
          > at
          > weblogic.ejb20.internal.MessageDrivenEJBHome.undeploy(MessageDrivenEJBHome.java:260)
          >
          > at
          > weblogic.ejb20.deployer.EJBDeployer.deactivate(EJBDeployer.java:1802)
          > at weblogic.ejb20.deployer.EJBModule.doDeactivate(EJBModule.java:865)
          > at weblogic.ejb20.deployer.EJBModule.deactivate(EJBModule.java:712)
          > at
          > weblogic.j2ee.J2EEApplicationContainer.deactivateModule(J2EEApplicationContainer.java:3161)
          >
          > at
          > weblogic.j2ee.J2EEApplicationContainer.deactivate(J2EEApplicationContainer.java:2186)
          >
          > at
          > weblogic.j2ee.J2EEApplicationContainer.deactivate(J2EEApplicationContainer.java:2131)
          >
          > at
          > weblogic.j2ee.J2EEApplicationContainer.stop(J2EEApplicationContainer.java:1915)
          >
          > at
          > weblogic.j2ee.J2EEApplicationContainerFactory.removeDeployedApplications(J2EEApplicationContainerFactory.java:761)
          >
          > at
          > weblogic.j2ee.J2EEApplicationService.shutdown(J2EEApplicationService.java:115)
          >
          > at
          > weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.shutdownHelper(DeploymentManagerServerLifeCycleImpl.java:257)
          >
          > at
          > weblogic.application.ApplicationService.prepareToSuspend(ApplicationService.java:46)
          >
          > at
          > weblogic.t3.srvr.SubsystemManager.prepareToSuspend(SubsystemManager.java:168)
          >
          > at weblogic.t3.srvr.T3Srvr.prepareToSuspend(T3Srvr.java:1085)
          > at
          > weblogic.t3.srvr.ServerLifeCycleWorkerThread.prepareToSuspend(ServerLifeCycleWorkerThread.java:51)
          >
          > at
          > weblogic.t3.srvr.ServerLifeCycleWorkerThread$1.run(ServerLifeCycleWorkerThread.java:35)
          >
          > at
          > weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
          >
          > at
          > weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
          > at
          > weblogic.t3.srvr.ServerLifeCycleWorkerThread.run(ServerLifeCycleWorkerThread.java:32)
          >
          > --------------- nested within: ------------------
          > weblogic.management.ManagementException: An error has occurred during
          > preDeregister().
          > nullmydomain:ApplicationRuntime=myserver_otis-dasl-ejb,EJBComponentRuntime=myserver_otis-dasl-ejb_otis-dasl-ejb.jar,Location=myserver,Name=myserver_otis-dasl-ejb_otis-dasl-ejb.jar_com.cibcwm.go.otis.dasl.submission.DASLSubmissionMdb_wls.mqs.dasl.dev.adp.reply3,ServerRuntime=myserver,Type=EJBTransactionRuntime
          > - with nested exception:
          > [javax.management.InstanceNotFoundException:
          > mydomain:ApplicationRuntime=myserver_otis-dasl-ejb,EJBComponentRuntime=myserver_otis-dasl-ejb_otis-dasl-ejb.jar,Location=myserver,Name=myserver_otis-dasl-ejb_otis-dasl-ejb.jar_com.cibcwm.go.otis.dasl.submission.DASLSubmissionMdb_wls.mqs.dasl.dev.adp.reply3,ServerRuntime=myserver,Type=EJBTransactionRuntime]
          >
          > at
          > weblogic.management.runtime.RuntimeMBeanDelegate.unregister(RuntimeMBeanDelegate.java:148)
          >
          > at
          > weblogic.ejb20.monitoring.EJBRuntimeMBeanImpl.unregisterDependents(EJBRuntimeMBeanImpl.java:58)
          >
          > at
          > weblogic.ejb20.monitoring.MessageDrivenEJBRuntimeMBeanImpl.unregisterDependents(MessageDrivenEJBRuntimeMBeanImpl.java:50)
          >
          > at
          > weblogic.ejb20.deployer.MessageDrivenBeanPoolInfoImpl.unInitPool(MessageDrivenBeanPoolInfoImpl.java:208)
          >
          > at
          > weblogic.ejb20.deployer.MessageDrivenBeanPoolInfoImpl.onUndeploy(MessageDrivenBeanPoolInfoImpl.java:121)
          >
          > at
          > weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.onUndeploy(MessageDrivenBeanInfoImpl.java:628)
          >
          > at weblogic.ejb20.internal.BaseEJBHome.undeploy(BaseEJBHome.java:203)
          > at
          > weblogic.ejb20.internal.MessageDrivenEJBHome.undeploy(MessageDrivenEJBHome.java:260)
          >
          > at
          > weblogic.ejb20.deployer.EJBDeployer.deactivate(EJBDeployer.java:1802)
          > at weblogic.ejb20.deployer.EJBModule.doDeactivate(EJBModule.java:865)
          > at weblogic.ejb20.deployer.EJBModule.deactivate(EJBModule.java:712)
          > at
          > weblogic.j2ee.J2EEApplicationContainer.deactivateModule(J2EEApplicationContainer.java:3161)
          >
          > at
          > weblogic.j2ee.J2EEApplicationContainer.deactivate(J2EEApplicationContainer.java:2186)
          >
          > at
          > weblogic.j2ee.J2EEApplicationContainer.deactivate(J2EEApplicationContainer.java:2131)
          >
          > at
          > weblogic.j2ee.J2EEApplicationContainer.stop(J2EEApplicationContainer.java:1915)
          >
          > at
          > weblogic.j2ee.J2EEApplicationContainerFactory.removeDeployedApplications(J2EEApplicationContainerFactory.java:761)
          >
          > at
          > weblogic.j2ee.J2EEApplicationService.shutdown(J2EEApplicationService.java:115)
          >
          > at
          > weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.shutdownHelper(DeploymentManagerServerLifeCycleImpl.java:257)
          >
          > at
          > weblogic.application.ApplicationService.prepareToSuspend(ApplicationService.java:46)
          >
          > at
          > weblogic.t3.srvr.SubsystemManager.prepareToSuspend(SubsystemManager.java:168)
          >
          > at weblogic.t3.srvr.T3Srvr.prepareToSuspend(T3Srvr.java:1085)
          > at
          > weblogic.t3.srvr.ServerLifeCycleWorkerThread.prepareToSuspend(ServerLifeCycleWorkerThread.java:51)
          >
          > at
          > weblogic.t3.srvr.ServerLifeCycleWorkerThread$1.run(ServerLifeCycleWorkerThread.java:35)
          >
          > at
          > weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
          >
          > at
          > weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
          > at
          > weblogic.t3.srvr.ServerLifeCycleWorkerThread.run(ServerLifeCycleWorkerThread.java:32)
          >
          > <Mar 3, 2004 1:48:33 PM EST> <Info> <Management> <BEA-141082>
          > <ServerRuntime:java.util.ConcurrentModificationException>
          > <Mar 3, 2004 1:48:33 PM EST> <Info> <Management> <BEA-141082>
          > <ServerRuntime:java.util.ConcurrentModificationException
          > at
          > java.util.LinkedList$ListItr.checkForComodification(LinkedList.java:552)
          > at java.util.LinkedList$ListItr.next(LinkedList.java:488)
          > at
          > weblogic.ejb20.deployer.EJBDeployer.deactivate(EJBDeployer.java:1801)
          > at weblogic.ejb20.deployer.EJBModule.doDeactivate(EJBModule.java:865)
          > at weblogic.ejb20.deployer.EJBModule.deactivate(EJBModule.java:712)
          > at
          > weblogic.j2ee.J2EEApplicationContainer.deactivateModule(J2EEApplicationContainer.java:3161)
          >
          > at
          > weblogic.j2ee.J2EEApplicationContainer.deactivate(J2EEApplicationContainer.java:2186)
          >
          > at
          > weblogic.j2ee.J2EEApplicationContainer.deactivate(J2EEApplicationContainer.java:2131)
          >
          > at
          > weblogic.j2ee.J2EEApplicationContainer.stop(J2EEApplicationContainer.java:1915)
          >
          > at
          > weblogic.j2ee.J2EEApplicationContainerFactory.removeDeployedApplications(J2EEApplicationContainerFactory.java:761)
          >
          > at
          > weblogic.j2ee.J2EEApplicationService.shutdown(J2EEApplicationService.java:115)
          >
          > at
          > weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.shutdownHelper(DeploymentManagerServerLifeCycleImpl.java:257)
          >
          > at
          > weblogic.application.ApplicationService.prepareToSuspend(ApplicationService.java:46)
          >
          > at
          > weblogic.t3.srvr.SubsystemManager.prepareToSuspend(SubsystemManager.java:168)
          >
          > at weblogic.t3.srvr.T3Srvr.prepareToSuspend(T3Srvr.java:1085)
          > at
          > weblogic.t3.srvr.ServerLifeCycleWorkerThread.prepareToSuspend(ServerLifeCycleWorkerThread.java:51)
          >
          > at
          > weblogic.t3.srvr.ServerLifeCycleWorkerThread$1.run(ServerLifeCycleWorkerThread.java:35)
          >
          > at
          > weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
          >
          > at
          > weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
          > at
          > weblogic.t3.srvr.ServerLifeCycleWorkerThread.run(ServerLifeCycleWorkerThread.java:32)
          >
          > >
          > <Mar 3, 2004 1:48:35 PM EST> <Critical> <WebLogicServer> <BEA-000217>
          > <Failed to fully suspend the server due to:
          > java.util.ConcurrentModificationException
          > java.util.ConcurrentModificationException
          > at java.util.HashMap$HashIterator.nextEntry(HashMap.java:782)
          > at java.util.HashMap$KeyIterator.next(HashMap.java:818)
          > at
          > weblogic.j2ee.J2EEApplicationContainerFactory.removeDeployedApplications(J2EEApplicationContainerFactory.java:751)
          >
          > at
          > weblogic.j2ee.J2EEApplicationService.shutdown(J2EEApplicationService.java:115)
          >
          > at
          > weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.shutdownHelper(DeploymentManagerServerLifeCycleImpl.java:257)
          >
          > at
          > weblogic.application.ApplicationService.forceSuspend(ApplicationService.java:82)
          >
          > at
          > weblogic.t3.srvr.SubsystemManager.forceSuspend(SubsystemManager.java:184)
          > at weblogic.t3.srvr.T3Srvr.forceSuspend(T3Srvr.java:1097)
          > at
          > weblogic.t3.srvr.ServerRuntime.uprotectedForceShutdown(ServerRuntime.java:629)
          >
          > at weblogic.t3.srvr.ServerRuntime.access$300(ServerRuntime.java:83)
          > at weblogic.t3.srvr.ServerRuntime$4.run(ServerRuntime.java:563)
          > at
          > weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
          >
          > at
          > weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
          > at weblogic.t3.srvr.ServerRuntime.forceShutdown(ServerRuntime.java:559)
          > at weblogic.t3.srvr.ServerRuntime.shutdown(ServerRuntime.java:547)
          > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
          > at
          > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
          >
          > at
          > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
          >
          > at java.lang.reflect.Method.invoke(Method.java:324)
          > at
          > weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:711)
          >
          > at
          > weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:690)
          >
          > at
          > com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
          > at
          > com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
          > at
          > weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:947)
          >
          > at
          > weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:908)
          >
          > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:946)
          > at
          > weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
          >
          > at
          > weblogic.management.runtime.ServerRuntimeMBean_Stub.shutdown(ServerRuntimeMBean_Stub.java:1184)
          >
          > at
          > weblogic.server.ServerLifeCycleRuntime$ShutdownRequest.execute(ServerLifeCycleRuntime.java:585)
          >
          > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
          > >
          > <Mar 3, 2004 1:48:35 PM EST> <Debug> <Management> <BEA-141132> <Dynamic
          > invocation while executing action shutdown on
          > mydomain:Location=myserver,Name=myserver,Type=ServerRuntime MBean
          > instance failed. The method shutdown with signature [int, boolean] was
          > invoked with parameters as [30, true].
          > java.util.ConcurrentModificationException
          > at java.util.HashMap$HashIterator.nextEntry(HashMap.java:782)
          > at java.util.HashMap$KeyIterator.next(HashMap.java:818)
          > at
          > weblogic.j2ee.J2EEApplicationContainerFactory.removeDeployedApplications(J2EEApplicationContainerFactory.java:751)
          >
          > at
          > weblogic.j2ee.J2EEApplicationService.shutdown(J2EEApplicationService.java:115)
          >
          > at
          > weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.shutdownHelper(DeploymentManagerServerLifeCycleImpl.java:257)
          >
          > at
          > weblogic.application.ApplicationService.forceSuspend(ApplicationService.java:82)
          >
          > at
          > weblogic.t3.srvr.SubsystemManager.forceSuspend(SubsystemManager.java:184)
          > at weblogic.t3.srvr.T3Srvr.forceSuspend(T3Srvr.java:1097)
          > at
          > weblogic.t3.srvr.ServerRuntime.uprotectedForceShutdown(ServerRuntime.java:629)
          >
          > at weblogic.t3.srvr.ServerRuntime.access$300(ServerRuntime.java:83)
          > at weblogic.t3.srvr.ServerRuntime$4.run(ServerRuntime.java:563)
          > at
          > weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
          >
          > at
          > weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
          > at weblogic.t3.srvr.ServerRuntime.forceShutdown(ServerRuntime.java:559)
          > at weblogic.t3.srvr.ServerRuntime.shutdown(ServerRuntime.java:547)
          > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
          > at
          > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
          >
          > at
          > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
          >
          > at java.lang.reflect.Method.invoke(Method.java:324)
          > at
          > weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:711)
          >
          > at
          > weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:690)
          >
          > at
          > com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
          > at
          > com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
          > at
          > weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:947)
          >
          > at
          > weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:908)
          >
          > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:946)
          > at
          > weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
          >
          > at
          > weblogic.management.runtime.ServerRuntimeMBean_Stub.shutdown(ServerRuntimeMBean_Stub.java:1184)
          >
          > at
          > weblogic.server.ServerLifeCycleRuntime$ShutdownRequest.execute(ServerLifeCycleRuntime.java:585)
          >
          > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
          > >
          >
          > Tom Barnes wrote:
          >
          >> Hi Dmitri,
          >>
          >> This is normal behavior.
          >> The internal rollbacks are a side effect of WL MDBs
          >> necessarily starting a transaction before they (internally)
          >> post a synchronous
          >> receive on the remote foreign JMS server. If the synchronous receive
          >> receives nothing, the tx is rolled back, and another
          >> synch receive is posted with a new tx. (When interacting with
          >> foreign vendors, tx MDBs usually must post synchronous receives
          >> in order to infect the received message - there is no
          >> standard JMS API for infecting asynchronously received messages
          >> with a user transaction.)
          >>
          >> Tom
          >>
          >> Dmitri Maximovich wrote:
          >>
          >>> Hi everybody,
          >>>
          >>> Is anybody successfully using remote IBM MQseries 5.3 server as
          >>> Foreign JMS in WLS 8.1sp2?
          >>> We're observing some strange behavior in this case. Here is our setup:
          >>>
          >>> WLS and IBM MQ server deployed on separate boxes.
          >>> WLS version 8.1sp2 running on Windows 2000/Intel
          >>> IBM MQ version 5.3 running on Solaris/SPARC
          >>>
          >>> We're using "WebSphere MQ classes for Java, version 5.303 -
          >>> j5303-L030225"
          >>> and "WebSphere MQ Extended Transactional Client Feature, version
          >>> 5.300 - j5303-L030122"
          >>>
          >>> MQ files added in WLS POST_CLASSPATH variable in WLS starup script.
          >>>
          >>> Foreign JMS server configured in WLS via fscontext JNDI.
          >>>
          >>> MDB bean deployed with Transaction attribute "Required".
          >>>
          >>> Everything seems to work fine, if we're posting message to MQ queue
          >>> MDB receives it and process successfully (just print message content
          >>> to the console for now).
          >>>
          >>> Problem: In WLS console, under Server->Monitoring->JTA->Monitor
          >>> inflight transactions we can constantly see one transaction enlisted
          >>> for our MDB bean with following details:
          >>>
          >>> =====================================================
          >>> Transaction ID: BEA1-00DFC5EB4B7B7F28EDB9
          >>> Coordinator: mydomain+myserver
          >>> Name: JMSMessagePoller.xxx.xxx.MyMessageProcessorMdb
          >>> Status: Active
          >>> Seconds Active: 17
          >>> Resources:
          >>> weblogic.ejb20.JMSConnectionPoller.xxx.xxx.MyMessageProcessorMdb=started
          >>> Properties
          >>> (key=value):
          >>> weblogic.transaction.name=JMSMessagePoller.xxx.xxx.MyMessageProcessorMdb
          >>> =====================================================
          >>>
          >>> This transaction seems to be Active for 30 seconds and then rolled
          >>> back (no error messages on WLS console displayed).On JTA statistics
          >>> page in WLS console "Total Rolled Back" counter keeps increneting
          >>> with every rollback.
          >>>
          >>> Does anybody observerd similar problem? May be it's normal behaviour
          >>> but I'm kind of worrying about those transactions and constant
          >>> rollback. I'd appreciate any feedback.
          >>>
          >>> ---
          >>> Sincerely,
          >>> Dmitri Maximovich
          >>
          >>
          >>

E-Recruiting search issue

Hi All,
We are using webdynpro screens for e-Rec. The internal candidate is not able to see the job posting when we do a search. I tried all combinations possible. The search for external candidate i.e. unregistered candidate search and registered candidate search for job postings is working. The data is present in backend. Trex is working fine beacuse all other searches are working fine. Any help will be appreciated.
Thanks.

Hi,
the easiest reason why a publication could be missing in the employee / internal candidate searches for postings would be no internal publication for the position. But i think this is the first thing you checked.
Next point to check is the posting channel configuration. Be sure that the internal posting channels are really set as internal in the customizing.
Furthermore you have to keep in mind that the standard publisher classes for internal and external channel 0001, 0002 have a hard coded check on these Ids in them. If you use other channel Ids for any reason, you have to copy the classes and replace this check.
If you use the standard internal posting channel 0001 check if the table T77RCF_INT_PUB contains the matching entry and the published flag.
The last point which comes to my mind spontaneously is table T77RCF_SRCH_ATTR. Especially i you try to use the unregistered search for employees, there are some release / patch levels which do not have this table filled properly. If there is no entry for the searches there, they won't show any hit.
The entries for the search for internal postings are:
EESearchPosting
EMPLOYEE2POSTING
UNREGEMPLOYEE2POSTING
Kind Regards
Roman

MT940 statement BACS DME auto clearing

Hi Friends,
Needed some help on automatic clearing of bank open items when processing electronic bank statement (MT940 format). When automatic payment is done through F110 , a DME file is created. In the bank statement config , the external transaction (NDDT) of HSBC bank is mapped to internal posting rule with clearing algorithm 019 - DME refrence number.
Bank in the MT940 statement must have BACS reference number.Usaually a 10 digit number if we use SAP delivered DME for BACS (GB_BACS). But this number does not appear in the file created. This can be seen in the details tab of the file. In the file created , there is another refrence which starts with SAPBACS00000xxxxx.(Note: a search string has been defined to pull the 10 digit numeric from this string). Earlier when i used to put this reference ..SAPBACS.... or the 10 digit number , open items used to be automatically cleared. Now it is not happening.
Does anyone have some more input on BACS items auto clearing during Electr Bank rec.
Regards
Ajit

Hi Ajit... I am also facing the same issue. Has your problem solved..
It would be of great help if u can give me u=your valuable inputs
cheers
sanjeev

BAPI_ACC_DOCUMENT_POST for Clearing (F-30)

How can we use BAPI_ACC_DOCUMENT_POST for Account posting with Clearing(F-30). I am able to do it for normal GL postings(FB01).I want to use this BAPI for clearing the Open items for a given customer...
Thanks
Rajesh

I don't think BAPI_ACC_DOCUMENT_POST is designed to perform a "Post with clearing". However, function module POSTING_INTERFACE_CLEARING will allow you to access the functionality of transaction FB05 (F-30 is really calling FB05 with BKPF-BLART = 'DA'). The FM documentation contains the following:
<i>Post with clearing (FB05) using internal posting interface
Function module 'POSTING_INTERFACE_CLEARING' creates a batch input transaction (or Call Transaction ... Using ...) for a document to be posted using transaction FB05.
The document header data and the data for the bank postings are transferred to table FTPOST. The rules for filling table FTPOST are described in the documentation for function module 'POSTING_INTERFACE_DOCUMENT'.
</i>
Best of luck!
Regards,
James Gaddis

Creating Z program for T code FBRA (resetting cleared item)

HI ABAP Gurus,
I have a requirement , please Help me.
One of my client Has executed APP program. through with 100 items are cleared. later they identified those invoice should not be cleared. To Reset this cleared item we have T code FBRA through which we can reset single line item each time.
So we need to develop a new program for Resetting all the items at one instance. Please guide how configure this??
Thanks in Advance
Babu

Yes AFAIK there is no standard report so you have to create your own with usage of FM POSTING_INTERFACE_RESET_CLEAR (*) "Jus" change the parameter of FBRA into SELECT-OPTIONS.
Regards,
Raymond
(*) FI Financial Accounting: Data Transfer Workbench; Accounting Documents: Data Transfer Workbench, Using the Internal Posting Interface.

Internal posting

Similar Messages

Maybe you are looking for