Peoplesoft delivered processes for HRMS

I am new to Peoplesoft. I am dealing with NA-payroll, and collected a basic idea related to HRMS. But still haven't got an overall idea about Peoplesoft HRMS. Will anyone guide me in having a basic documentation for HRMS especially about delivered processes.

If you have access to the Oracle University training courses, they can be the best resourse for a beginner. Yoy can find lots of introductory courses for all the modules of PeopleSoft there.
In addition, keep reading PeopleBooks :)
All the best !

Similar Messages

Looking for Documentation on PeopleSoft Delivered App Packages.

Hey Guys,
Do anyone know whether PeopleSoft provide documentation for the Delivered App Packages.
I'm expecting something like Java documentation, we get complete documentation like complete list of classes, respective methods, properties, and relation with other classes and packages.
It would be really helpful, if there is any documentation something similar for PeopleSoft Delivered Packages too.
Thanks in advance.
-M

I've been looking for something similar. There is some interesting stuff around the CDM for PeopleSoft CRM:
http://bloggingaboutoracleapplications.org/creating-peoplesoft-crm-worker-using-cdm-classes/
However nothing as comprehensive as JavaDoc for PeopleSoft - well that I know of anyway.

Down payment process for Poland, new business process or not ?

Hello,
I'm a little bit confused about implementation down payment process for Poland.
The OSS-notes 818079 and 1007635 describe a solution for this.
How do I have to implement the correct down payment process for Poland ? Do I have to create an extra business process with new sales order type, new billing type, separate calculation procedure, new output type and so on ?
Or is it possible to use existing business processes in sales and distribution for down payment processes ?
Thanks in advance
Holger

hi,
Check the process for down payment processing
The following Customizing settings have to be made for down payment processing:
Settings for the billing plan - To activate the billing plan function, maintain the materials, for which you wish to process down payments, with item category group 0005 (milestone billing). This gives the item type TAO via item type determination. The item type TAO calls up the billing plan function.
You need to implement the following activities in the billing plan for down payments:
Maintain deadline category - This determines the billing rule (percentage or value down payment) for the down payment request. The system assigns billing type FAZ (payment request) defined in the standard system with billing category P. (For the billing type FAZ there is the cancellation billing document type FAS in the standard system).
Maintain the deadline proposal - Use the down payments that are due for the proposed deadlines.
Maintaining a Pricing Procedure with the Condition Type AZWR:
In the standard system the condition type AZWR is delivered for the down payment value already provided but which has not yet been calculated. You must include this condition type in the relevant pricing procedure before output tax.
Enter condition 2 (item with pricing) and the calculation formula 48 (down payment clearing value must not be bigger than the item value) for the condition type AZWR.
Before the condition AZWR you can create a subtotal with the base value calculation formula 2 (net value). If the condition AZWR is changed manually, you can get information on the original system proposal from the subtotal.
Maintain the printing indicator - The pricing procedure can not be marked as a transaction-specific pricing procedure (field Spec.proc.) The condition type AZWR has the calculation type B (fixed amount) and the condition category E (down payment request / clearing).
Maintaining the Billing Document - In the standard system there is the billing type FAZ (down payment request) and the billing type FAS for canceling . The down payment is controlled using the billing category P of the billing type. A billing type becomes a down payment request when the billing category P is assigned. You have to maintain blocking reason 02 (complete confirmation missing) for the billing documents and assign it to billing type FAZ.
Copying control - Copying requirement 20 must be entered in copying control at item level for the down payment request. In the standard system the order type TA for copying control is set up according to the billing type FAZ for the item category TAO.
Copying requirement 23 must be entered in copying control at item level for down payment clearing. In the standard system the order type TA for copying control is set up according to the billing type F2 for the item category TAO.
Financial Accounting settings - A prerequisite for down payment processing is that the account is assigned to the underlying sales document. To do this, change the field status settings in Customizing as follows:
Set reconciliation accounts (transaction OBXR) - For the `received down payments' and `down payment requests' from
the G/L accounts you have selected, you should assign the field status definition G031.
Maintain accounting configuration (transaction OBXB) - For the down payments (posting key ANZ in the standard system) and the output tax clearing (posting key MVA in the standard system), you must maintain the posting key.
You must also carry out a G/L account number assignment for the tax account.
Maintain the posting key (transaction OB41) - For posting key 19, set the sales order as an optional field !!!
Maintain the field status definition (transaction OB14) - For field status variant 0001, field status group G031, set the
sales order as an optional field !!!
Assign the company code to the field status variants (transaction OBC5)
chandu

What is the internal processing for idocs

Dear friends this is subbu working as a abap consultant.
can any body explain the how idocs are transfered (inbound process and outbound process)

1.Here out bound means sender.Inbound mens --receiver.
Data Creation in Idoc
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
IDoc is a intermediate document to exchange data between two SAP Systems.
*IDocs are structured ASCII files (or a virtual equivalent).
*Electronic Interchange Document
*They are the file format used by SAP R/3 to exchange data with foreign systems.
*Data Is transmitted in ASCII format, i.e. human readable form
*IDocs exchange messages
*IDocs are used like classical interface files
IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
FOr testing you can use WE19.
How to create idoc?
*WE30 - you can create a IDOC type
For more information in details on the same along with the examples can be viewed on:
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30 )
Create Message Type ( WE81 )
Assign Idoc Type to Message Type ( WE82 )
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
Check these out..
Re: How to create IDOC
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
go trough these links.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
2.IDOCs are independent of the sending and receiving systems.
3.IDOCs are independent of the direction of data exchange.
The two available process for IDOCs are
Outbound Process
Inbound Process
AND There are basically two types of IDOCs.
Basic IDOCs
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extended IDOCs
Extending the functionality by adding more segments to existing Basic IDOCs.
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
imp links
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
www.sappoint.com
--here u can find the ppts and basic seetings for ALE
http://sappoint.com/presentation.html
www.sapgenie.com
http://www.sapgenie.com/ale/index.htm
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
Try this..Hope this will help.
SAP ALE & IDOC<<<<
Steps to configuration(Basis) >>
1. Create Logical System (LS) for each applicable ALE-enabled client
2. Link client to Logical System on the respective servers
3. Create background user, to be used by ALE(with authorizaton for ALE postings)
4. Create RFC Destinations(SM59)
5. Ports in Idoc processing(WE21)
6. Generate partner profiles for sending system
The functional configuration(Tcode: SALE)
Create a Customer Distribution Model (CDM);
Add appropriate message types and filters to the CDM;
Generate outbound partner profiles;
Distribute the CDM to the receiving systems; and
Generate inbound partner profiles on each of the clients.
Steps to customize a new IDoc >>>
1. Define IDoc Segment (WE31)
2. Convert Segments into an IDoc type (WE30)
3. Create a Message Type (WE81)
4. Create valid Combination of Message & IDoc type(WE82)
5. Define Processing Code(WE41 for OUT / WE42 for IN)
6. Define Partner Profile(WE20)
Important Transaction Codes:
SALE - IMG ALE Configuration root
WE20 - Manually maintain partner profiles
BD64 - Maintain customer distribution model
BD71 - Distribute customer distribution model
SM59 - Create RFC Destinations
BDM5 - Consistency check (Transaction scenarios)
BD82 - Generate Partner Profiles
BD61 - Activate Change Pointers - Globally
BD50 - Activate Change Pointer for Msg Type
BD52 - Activate change pointer per change.doc object
BD59 - Allocation object type -> IDOC type
BD56 - Maintain IDOC Segment Filters
BD53 - Reduction of Message Types
BD21 - Select Change Pointer
BD87 - Status Monitor for ALE Messages
BDM5 - Consistency check (Transaction scenarios)
BD62 - Define rules
BD79 - Maintain rules
BD55 - Defining settings for IDoc conversion
WEDI - ALE IDoc Administration
WE21 - Ports in Idoc processing
WE60 - IDoc documentation
SARA - IDoc archiving (Object type IDOC)
WE47 - IDoc status maintenance
WE07 - IDoc statistics
BALE - ALE Distribution Administration
WE05 - IDoc overview
BD87 - Inbound IDoc reprocessing
BD88 - Outbound IDoc reprocessing
BDM2 - IDoc Trace
BDM7 - IDoc Audit Analysis
BD21 - Create IDocs from change pointers
SM58 - Schedule RFC Failures
Basic config for Distributed data:
BD64: Maintain a Distributed Model
BD82: Generate Partner Profile
BD64: Distribute the distribution Model
Programs
RBDMIDOC Creating IDoc Type from Change Pointers
RSEOUT00 Process all selected IDocs (EDI)
RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
RSARFCEX - Execute Calls Not Yet Executed
RBDMOIND - Status Conversion with Successful tRFC Execution
RBDMANIN - Start error handling for non-posted IDocs
RBDSTATE - Send Audit Confirmations
FOr testing you can use WE19.
There are two filtering in IDoc.
Segment Filtering:
Segment filtering can be achieved using T/Code BD56. Here you can suppress a whole segment irrespective of data inside it . You have to give Message Type / Sender Prrtner / Receiver Partner.
Data Filtering:
Data filtering can be done in dustribution model (BD64) where you can restrict whole IDOCS or partials IDOCS to be send based on data in fields inside IDOC depending on whether the segment in which you filter is at the highest level or at a lower level. For example in MATMAS if you put a filter of E1MARCM for a particular plant , only data for this plant will go and other plants will be ignored.
Please check this link for more information.
http://help.sap.com//saphelp_470/helpdata/EN/0b/2a611c507d11d18ee90000e8366fc2/frameset.htm
Reward points..

SD process for service process

hi
what will be the SD flow for service process i.e i'm trying to create a service as a material ( for logistics service providers ).i need to do shipment.
i have created a material as a service(material type - DIEN), and i have created a sales order and O/B delivery is automatically created for that material . but i could not include that material in the shipment.
kindly post ur suggestions.
regards
shankar

Servide process in Sd scenario's are basically order related billing. The term order related billing will be much clear after I narate an example. If we speak of Rentals for housing or commercial, we are not physically delivering the product while billing. Hence we have a sales order & based on sales order, we directly bill the customer.
Another example is in third party scenario, we receive order from customer. as we do not manufacture that product, we place an order to vendor instructing the vendor to directly deliver to our customer. Though a product is being delivered, it is not being delivered from our plant, hence we do not create delivery in our system, but we certainly bill the customer. This again is order related billing, as we have indirectly provided a service to the customer, & also added our business volumes.
The above are process for services.
Regards,
Rajesh Banka
Reward points if helpful.

Process for Impairment of asset

Hi,
Please expalin me the process for impairment of asset. my client want to perform impairment process for one of the assets.
Thanks&Regards,
Bhaskar Suruvu

Hi,
In some countries, it is legally required that companies calculate depreciation after asset impairment. To do this, you have to use specific depreciation rates and base values that are contained in a special formula. The localization of the New Depreciation Engine for these countries implements this formula and enables you to calculate asset depreciation after impairment postings have been made, in accordance with the requirements. The following depreciation keys are delivered for this purpose:
Depreciation Key                                                                                Description
IDB                                                         Declining balance method for impairment with 5% scrap value
IDM                                                        Declining balance method for impairment with 0% scrap value
ILI                                                          Straight-line method for impairment with 0% scrap value
ILT                                                         Straight-line method for impairment with 5% scrap value
Features: Each depreciation key calculates depreciation using a specific formula, as follows:
●     Depreciation key IDB
Depreciation = Book value after impairment * Rate
where Rate is calculated as: 1 - (( Remaining Value / Book value after impairment )1/Remining useful life).
Depreciation is calculated in the following years based on the net book value of an asset.
●     Depreciation key IDM
Depreciation in the year of impairment = Book value after impairment * Rate * 10/9
where Rate is calculated as: 1 u2013 0.11/Remining useful life.
Depreciation in the following years = Remaining depreciable value * Rate * 10/9
where Remaining depreciable value is calculated as: book value after impairment * ( 1 u2013 Rate ) past years.
●     Depreciation key ILI
Depreciation = Book value after impairment * 1 / n
where n is remaining useful life.
●     Depreciation key ILT
Depreciation = ( Book value after impairment u2013 remaining value ) * 1 / n
where n is remaining useful life.
Hope this helps.
Rgds
Manish

Business Process for Invoice receipting

The company is an SME with seven offices distributed around Australia. Purchase requisitions have a rigorous approval procedure. The requisitioner needs the correct approval before a purchase order is created.
However we do not have a process for ensuring that the goods have been delivered or services provided when the invoice comes into Finance for paying. We do not have inventory, very few assets, but do purchase many services. The only people who can advise if the services have been rendered would be the requisitioner on the requisition.
Is there a business process that can be triggered off by receipt of the invoice? Is there a workflow to send a request to the requisitioner to acknowledge the Invoice receipt? Is invoice receipting different from goods receipting? Is the Goods Receipt non valuated flag on the PO the determining factor for invoice receipting? Is the transcation for invoice receipting MIGO? Are there any SAP papers on best practices that are not aimed at cement companies or retail?

Dear,
There 2 points:
1. Service Acceptance Sheet (for services)
2. Quality notification maintenance in purchase order (for goods receipt).
Please check these 2 options, I hope that these two features can provide answers to you most of your questions.
Invoice receipt is differ from Goods receipt and more over Free items in PO definitely have impact on Invoice receipt.
Regards,
Syed Hussain.

ATTN: SSHR Rollup 3 for HRMS FP.K Rup 5671710

The SSHR Rollup 3 for HRMS FP.K Rup patch 5671710 has just been released today.
This patch contains fixes for the following bugs:
Bug 5612687 : ORACLE.APPS.FND.FRAMEWORK.OAEXCEPTION: FOR CHANGE MANAGER PROCESS.
Bug 5590776 : POSITION DEFAULTING AND POSITION LOV NOT WORKING IN RFC NOTIFICATIONS
Bug 5587674 : ONDEMAND:OHS: SEARCH IN SELFSERVICE HAS DUPLICATE VALUES FOR ASG
Bug 5582127 : ESC:PROPOSED_SALARY_N CONTAINS 38 DIGITS AFTER DECIMAL FROM SSHR.
Bug 5572041 : THIS PERSON IS NOT ELIGIBLE FOR THE ELEMENT ASSOCIATED WITH THIS ABSENCE TYPE.
Bug 5522407 : EMPLOYEE'S RECORD OR ELIGIBILITY CHANGED ERROR WHEN ADDING EMERGENCY CONTACT.
Bug 5515312 : SSHR SALARY CHANGES AUTOMATICALLY WHEN USING BACK BUTTONS.
Bug 5501388 : ONDEMAND:CANNOT ENTER REQUIRED FIELDS FOR JAPAN HIRE PROCESS.
Bug 5468591 : VOL TERM OF A MGR RESULTS IN INVALID ERROR MESSG -DUE TO SUB-ORD FUTURE ASSG CHG.
Bug 5527923 : GENERIC ADDRESS STYLE IS BEING REPLACED IN SELF SERVICE CONTACTS FORM.
Bug 5515814 : ONDEMAND:IN SSHR WHEN TERMING AND REHIRING AN EMP THE PARTY ID # IS NOT THE SAME.
Bug 5508360 : CHANGE JOB FUNCTION POSITION QUERY RETURN ONLY 'ACTIVE' STATUS POSITIONS.
Bug 5507401 : MANAGER SSHR HIRE APPLICANT GIVES NUMERIC OR VALUE ERROR WHEN ADDING SUPERVISOR.
Bug 5328872 : WRONG EVENT PASSED TO FINALIZETRANSACTION CALLBACK FOR DELETE ACTION ON SFL.
Bug 5138131 : DEFAULT VALUES IN EXTRA INFORMATION DFF IN SELF SERVICE NOT DISPLAYED
Bug 5652542 : THE EMPLOYEE'S RECORD OR ELIGIBILITY STATUS HAS CHANGED ERROR.
This patch requires additional prerequisite patches to have been successfully applied to your system before it can be applied. These prerequisite patches, as at the time that this patch was built, are listed below. Please check Oracle Metalink to determine if any of these have been superseded.
11i.HR_PF.K.delta.1 - 11I.HR_PF.K RUP 1
Regards,
Greg

We need to know the new codes which will be added and which if any will be replaced. We know those identified on the US Gov site but can Oracle Dev. provide the specifics in advance so we can update our Employment Applications etc to match Oracle HR definitions?
Regards,
Ed

Error in executing a process for compilation for jsp

We have an iView which has jsp pages in it. We deployed the par & try toaccess the iview & we get an exception. The issue is that the iview has a jsp page. At the run time, this jsp is converted into a .java file
without problem. But EP engine is having issues compiling this java fileinto .class file.
On the other hand this same iview works just fine on our windows installation. Only Solaris EP install is having problems. The version onwindows as well as on Solaris is EP6 SP9.
Here is the exact version on the solaris EP:
sap.com/SAP-JEECOR 6.40 SP9 (1000.6.40.9.0.20041119045253) 20041122132733
sap.com/SAP-JEE 6.40 SP9 (1000.6.40.9.0.20041119045409) 20041122132741
When I copy the .class file from windows to unix machine, the iView works fine. Here is the exception I am getting:
>>> JSPCompiler >>> error
[email protected]a188b
[EXCEPTION]
com.sapportals.portal.prt.servlets_jsp.server.compiler.CompilingException:
Error in executing a process for compilation
at
com.sapportals.portal.prt.servlets_jsp.server.compiler.impl.J2eeCompiler_6_30.launchCompilerProcess(J2eeCompiler_6_30.java:574)
at
com.sapportals.portal.prt.servlets_jsp.server.compiler.impl.J2eeCompiler_6_30.compileExternal(J2eeCompiler_6_30.java:370)
at
com.sapportals.portal.prt.servlets_jsp.server.compiler.impl.J2eeCompiler_6_30.compile(J2eeCompiler_6_30.java:672)
at
com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPParser.parse(JSPParser.java:2143)
at
com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPCompiler.compile(JSPCompiler.java:76)
at
com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPCompiler.run(JSPCompiler.java:122)
at
com.sapportals.portal.prt.core.broker.JSPComponentItem.compileJSP(JSPComponentItem.java:279)
at
com.sapportals.portal.prt.core.broker.JSPComponentItem.getComponentInstance(JSPComponentItem.java:129)
at
com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.service(PortalComponentItemFacade.java:355)
at
com.sapportals.portal.prt.core.broker.PortalComponentItem.service(PortalComponentItem.java:934)
at
com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:435)
at
com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:527)
at
com.sapportals.portal.prt.component.AbstractComponentResponse.include(AbstractComponentResponse.java:89)
at
com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:232)
at com.sapportals.portal.htmlb.page.JSPDynPage.doOutput(JSPDynPage.java:76)
at
com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:129)
at
com.sapportals.portal.htmlb.page.PageProcessorComponent.doContent(PageProcessorComponent.java:134)
at
com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at
com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at
com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at
com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at
com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at
com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:646)
at
com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at
com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at
com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at
com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
at
com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:232)
at
com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
at java.security.AccessController.doPrivileged(Native Method)
at
com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:153)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)
at
com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
at
com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
at
com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
at
com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821)
at
com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at
com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
at
com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
at
com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at
com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
I am having the same issue with another iview which has jsp page in it.
The web dynpro iview works fine.

Hi, seems like there's some typo in your jsp. Check the .java file listed with a java editor (like eclipse or devstudio.). Maybe you'll find the typo this way faster.
Most often, a multiline page import hampers jsp compilation,
e.g.
<%@page import="java.util.List,
java.util.Map"%>
needs to be
<%@page import="java.util.List,java.util.Map"%>
Regards,
Armin

Error in executing a process for compilation

Hi:
Our portal version is 6.0.2.28.0 (SAPJ2EE PL29)
we have the following problem:
1.- the developer upload a component in portal, but when he tries to run it, the following error appears:
Mar 28, 2005 4:22:06 PM # Client_Thread_8 Fatal >>> JSPCompiler >>> ERROR in Compiling :JSPFileInfo :4782283
JSP File : /usr/sap/J2EE_DP3/j2ee/j2ee_00/cluster/server/services/servlet_jsp/work/jspTemp/irj/root/WEB-INF/portal/portalapps/PRUEBA
_PCCLibragestMostrarPlantillas/pagelet/MostrarPlantillas.jsp
Class Name: sapportalsjspMostrarPlantillas
Java File : /usr/sap/J2EE_DP3/j2ee/j2ee_00/cluster/server/services/servlet_jsp/work/jspTemp/irj/root/WEB-INF/portal/portalapps/PRUEB
A_PCCLibragestMostrarPlantillas/work/pagelet/_sapportalsjsp_MostrarPlantillas.java
Package Name : pagelet
Class File : /usr/sap/J2EE_DP3/j2ee/j2ee_00/cluster/server/services/servlet_jsp/work/jspTemp/irj/root/WEB-INF/portal/portalapps/PRUE
BA_PCCLibragestMostrarPlantillas/work/pagelet/_sapportalsjsp_MostrarPlantillas.class
Is out dated : false
com.sapportals.portal.prt.servlets_jsp.server.compiler.CompilingException: Error in executing a process for compilation
2.- If I stop/start SAPJ2EE the component, which was uploaded before,can be run without problem, but if you upload it again,when you try to run it again, the compilation error appears
Any suggestion???
Thanks

Hi:
the problem was not resolved deleting/uploading the components, the problem was resolved increasing the memory in the host and tuning the JVM memory parameters.
In our host the memory was reduced and this was the origin of the problem
Thanks

Error in executing a process for Flex compilation ....exceeds 32K...

Hi,
deployin my model i get the following error-message.
"Error in executing a process for Flex compilation, Error: Branch between 64935 and 97770 around line 0 exceeds 32K span. If possible, please refactor this component.
Error: Branch between 64935 and 97770 around line 0 exceeds 32K span."
Do i delete a sort-element from my model it is deployed very well. So what does this message exactly mean and how can I locate where the error occurs and how can i fix that problem because i need this sort-element to be in my model.
Thanks for your help!
Tobias

Hi Tobias,
You are receiving this error due to a current limitation in the Flex server. How you can fix this is to split the iView you are currently working on into two iViews, and embed one within the other. This will decrease the size of the current iView you are receiving the error for and eliminate this problem.
Hope this helps
Cheers,
Scott

Regarding Goods Reversal and Goods Issue process for Production orders

Hi,
I have a issue regarding Goods Reversal and Goods Issue process for Production orders.
Actually I am having a Z - Function Module in that i am passing production order number other details to
make the Goods Reversal happen.
The code for the above is as below:
 i_mvtit-material = wa_mdfa-matnr.
 i_mvtit-plant = i_resb-werks.
 i_mvtit-spec_stock = 'Q'. "New
 i_mvtit-stge_loc = 'ZWIP'.
 i_mvtit-stge_type = i_resb-lgtyp. "New
 i_mvtit-batch = i_resb-charg. "New
 i_mvtit-orderid = i_resb-aufnr.
 i_mvtit-spec_stock = i_resb-sobkz.
 i_mvtit-entry_qnt = i_resb-enmng.
 i_mvtit-entry_uom = i_resb-erfme.
 i_mvtit-entry_uom_iso = i_resb-meins. "New
 i_mvtit-wbs_elem = v_frwbs.
 i_mvtit-move_type = '262'.
 i_mvtit-xstob = 'X'.
 i_mvtit-gr_rcpt = i_resb-aufnr. "New
 i_mvtit-reserv_no = i_resb-rsnum.
 i_mvtit-res_item = i_resb-rspos.
 APPEND i_mvtit.
* HEADER ELEMENTS
 k_gmvt_code-gm_code = '03'.
 k_gmvt_head-pstng_date = sy-datum.
 k_gmvt_head-doc_date = sy-datum.
* CREATE GOODS MOVEMENTS
 CALL FUNCTION 'BAPI_GOODSMVT_CREATE'
 EXPORTING
 goodsmvt_header = k_gmvt_head
 goodsmvt_code = k_gmvt_code
 TABLES
 goodsmvt_item = i_mvtit
 return = i_return.
The Above code does the Goods Reversal but then i will update one Z Table with fields like
Production Order Number[AUFNR], Number of Reservation[RSNUM], Item Number of Reservation [RSPOS], Material Number [MATNR], Requirement Quantity [BDMNG], WBS element[PSPNR] etc. If Above BAPI runs sucessfully.
That is happening correctly.
But Then actual issue is i have do Goods Issue for those Z-Table records.
There i will give Production order Number's & Storage Location in Selection-Criteria.
Then i need to do Goods Issue for that order.
The code i had written as follows.
* POPULATE VALUES FOR BAPI CALL
 i_mvtit-material = i_zpsi7603_01-matnr.
 i_mvtit-plant = i_resb-werks.
 i_mvtit-spec_stock = 'Q'. "New
 i_mvtit-stge_loc = p_sloc.
 i_mvtit-stge_type = i_resb-lgtyp. "New
 i_mvtit-batch = i_resb-charg.
 i_mvtit-orderid = i_resb-aufnr.
 i_mvtit-spec_stock = i_resb-sobkz.
 i_mvtit-entry_qnt = i_resb-enmng.
 i_mvtit-entry_uom = i_resb-erfme.
 i_mvtit-entry_uom_iso = i_resb-meins. "New
 i_mvtit-wbs_elem = v_frwbs.
 i_mvtit-move_type = c_261.
 i_mvtit-mvt_ind = 'F'. "New
 i_mvtit-xstob = c_x.
 i_mvtit-gr_rcpt = i_resb-aufnr. "New
 i_mvtit-reserv_no = i_resb-rsnum.
 i_mvtit-res_item = i_resb-rspos.
 APPEND i_mvtit.
* HEADER ELEMENTS
 k_gmvt_code-gm_code = c_03.
 k_gmvt_head-pstng_date = sy-datum.
 k_gmvt_head-doc_date = sy-datum.
* CREATE GOODS MOVEMENTS
 CALL FUNCTION 'BAPI_GOODSMVT_CREATE'
 EXPORTING
 goodsmvt_header = k_gmvt_head
 goodsmvt_code = k_gmvt_code
 TABLES
 goodsmvt_item = i_mvtit
 return = i_return.
 CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
 EXPORTING
 wait = c_x.
 READ TABLE i_return INDEX 1.
 IF i_return-type EQ c_s.
 DELETE FROM zpsi7603_01 WHERE aufnr = i_resb-aufnr AND
 rsnum = i_resb-rsnum AND
 rspos = i_resb-rspos.
 ENDIF.
If i run above code for Goods Issue it is giving error can anybody tell me what changes i need to do to make it work.
The Error Message i am getting is as below:
Qty and / or "delivery completed" ind. or final issue ind. are missing
Error Number for the above is : 264.
Can anybody solve my issue.
Any help will be appreciated.
Thanks in advance.
Thanks & Regards,
Rayeez.

Hi,
Thanks boss.
It is working now correctly.
The issue is the i_mvtit-XSTOB should be equal space in case of Goods issue while incase of Reversal it should be equal to X.
Thanks for ur efforts.
I had awarded you points.
Thanks a lot.
Thanks & Regards,
Rayeez.

Process for porting phone # to FIOS?

Can someone point me to instructions on how to port my # from Comcast/Xfinity to FIOS?
We had FIOS for years until five weeks ago, switched to Xfinity and ported the home # I've had for 10 years, then switched back to FIOS yesterday. During the ordering process with FIOS we were clear that we wanted to port in our #. During the last contact with FIOS before installation they told my husband to wait a week after switching to call to port the #, and the installer yesterday issued us a new # (which he said would be temporary). FIOS service was closed by the time the installation was done yesterday, and is closed today. What is the process for porting the #? Is there a place online we can do this when FIOS is closed? How long before Xfinity releases the #? If I lose this # that is connected to basically every other account I have, I will be furious.

In March I switched my phone from Vonage to VZ digital voice. I did this so I was able to get a better bundled price.
I informed the VZ CS that my intent is to move my phone from Vonage to VZ. They told me that it will take 5 days for this to occur and a truck roll would need to be scheduled. On the day of the appointment my number continued to work with vonage. The VZ tech arrived, wired up the home phone line to the ONT and the phone line was dead. She went to the truck and whatever magic occurred she returned 5 minutes later and told me to see if I had dial tone. Upon picking up the phone there was dial tone. I called my cell and it displayed the caller ID of my phone. I then called my home phone and it worked too.
Since you already have dial tone I'm sure no truck roll will be necessary. I do understand there is a 5 day porting process but once you call TS and tell them your intent it should be pretty straight forward. When I plaecd my original order it was documented on that order. Not sure if this helps but hope it does.
Jim

Increase the number of portions in process for each conversion object

I experts,
I configured SAP TDMS 3.0 with SP 14 to transfer test data from QAS to DEV (both is ECC 6.0) for the first test with TDMS TIM (Time Based Reduction).
The data transfer phase is still running (99% - 60hs running). We analyzed the Display Runtime Information report and see that objects of conversion with similar calc. records and calc. GBytes have very different the Net Runtime.
TMDS currently is working with four objects of conversion, processing a portion of each.
Conversion objects that are running are:
- Z_LTBP_002
- Z_TSEGE_002
- Z_VEVW_002
- Z_YST27_002
We check in the receiver system, and we see that is use only one DIA process to update the each table.
How can increase the performance of the update? Is correct that use only 1 DIA process for this??
Can I increase the number of portions in process for each conversion object?
Any help is greatly appreciated.
Regards,
Sergio

Hi,
Check SAP Note 916763 - TDMS performance composite SAP note
Note 890797 - SAP TDMS - required and recommended system settings
Thanks
Sunny

Standard Process for Credit Memo & Debit Memos in CRM

Dear all,
What is the standard process for Credit Memo and Credit Memo Creation within CRM Complaint Transaction?
We can successfully replicate Return Items and Replacement Items in ECC Return Order
But I don't know how to process Credit Memo and Debit Memo in ECC.
What are the Accounting Implications takes place once we create and release the credit memo / Debit memo in CRM Complaint Transaction?
How to see the entire document flow?
I can create Credit Memo for a Returned Line Item in CRM without any errors. But I could not see any follow-up transaction or process either in CRM or ECC.
Kindly educate me in this regard. Your suggestions are highly appreciated
Best regards
Raghu ram
Edited by: Raghu Ram on Jun 23, 2010 6:29 PM
Edited by: Raghu Ram on Jun 25, 2010 8:30 AM

Hi suchi,
The following would be very useful to you.
To reduce implementation time for print forms development, SAP has created a set of the most commonly used forms - Preconfigured Smart Forms:
SD: Invoice, Quotation, Contract, Delivery Note, Order Confirmation, Scheduling Agreement, Inquiry, Cash Sales, Picking List
MM: Purchase Order, Request for Quotation, Contract, Delivery Schedule, Good Issue (3 scenarios), Good Receipt (3 scenarios)
FI: Dunning Notice
All can easily adapt these forms to their requirements, saving time and money.
Hope this information has been useful to you.
if you would like to have a smartform of your own i.e a Z or a Y then there is an option to get a sap script copied onto a smartform.
the sap script for the same is -> F140_DOCU_EXC_01
Go to Txn SMARTFORMS and just put the required smart form name in FORM field and then go to the menu bar: Utilities-> Migrate SAPScriptForm and juts type in the Script name which is given above(i.e F140_DOCU_EXC_01 )
I hope this will be an amicable solution.
if helpful pls reward.
Thanks
Venugopal

Peoplesoft delivered processes for HRMS

Similar Messages

Maybe you are looking for