Flexible Appraisal Process Flow EHP-7, Where to start???

Hi Experts,
Can anybody please guide me how to go about capturing the Flexible Appraisal Process Flow.
Where exactly it starts & where it ends, i am not able to visualize the same.
Shall i start with Templete creation??
Please guide me a bit on this.

Hi,
I guess my document can help you out.
Objective Setting and Appraisals : Appraisal Template Configuration and it's flexibility using available BADIs
Regards
Sounak

Similar Messages

Predefined appraisal process and flexible appraisal process

Hello
I read the new presentation about the New in Performance Management (SAP enhancement package 4
For SAP ERP 6.0) I don't understand the connection between predefined appraisal process and flexible appraisal process.
Can I use these 2 processes together?
Is the new "Predefined Performance Management Process: Calibration" work with flexible appraisal process or this is 2 different system and process?
For example This process of predefined appraisal compare "final appraisal" of workers. Where this "final appraisal" is stored . In which question of the appraisal form ?
In the presentation Sap wrote "Team calibration based on overall appraisal". What is "overall appraisal" in terms of appraisal form ?

Hi,
so to answer your questions:
Can I use these 2 processes together?
No these are 2 different functionalities. The reason they were delivered at the same time is because they are using the same technology (web dynpro)
Thus the 'calibration' which is designed for Predefined does not exist for Flexibe.
So with EHP4 SAp delivered the new Predefined functionality
and the Flexible which is basically the same functionality as before but using web dynpro instead of BSP page.
Regarding "Team calibration based on overall appraisal". This functionality allows manager to compare the individual appraisal documents of the employees that reports to him.
You can find some more information on these fucntionalities in SAP help link below
http://help.sap.com/erp2005_ehp_04/helpdata/en/cd/dae8a24ab011d18a0f0000e816ae6e/frameset.htm
Hope this help
Sarah

Performance Management EHP4 Flexible Appraisal Process

Hi
We are in the process of building Performance Management using Enhancement Package 4 in ECC 6.0 in our test system. We have activiated flexible appraisal process and have completed the necessary config for ESS and MSS and appraisal template.
The MSS user can create the appraisal and define the objectives etc. The ESS user can view the appraisal but cannot add comments. On checking the appraisal template we have created a criteria for employee comments and an element called additional comments the tab 'element access' has been marked against the employee as follows:
Participant = Employee
Plan:Access = Change
Review Access = Change
Completed = Display
So we do not know why the ESS user cannot add comments.
Can anyone help on this issue?
Many thanks
Julie

Many thanks for this - we have checked the template level and have the column access for column 'objectives' (which is what is used at element level for appraisee comments) and if we change the column owner to 'appriaser and appraisee' it works for the appraisee but not for the appraiser. So we have a choice either it is set to appraiser and it works fine for the manager or we change it to appraisee and appraiser and it works fine for the ESS user.
Perhaps there is something else we need to check?

Flexible appraisal processes & predefined Performance Management process.

Good Night.
What is the diference between Flexible appraisal processes & predefined Performance Management process and in what case i have that use it?
Kind Regards-

Hi Juan,
Flexible Appraisal Porcess- As the name suggest you have the flexibilty to design your apparisal templates using the functionalities provided by SAP.
For eample: Using transaction PHAP_Catalog_PA or OOAM, you can design your apparsail template.
Predefined Appraisal Template: Again as the name suggest, SAP has pre-designed the strucure for defining the appraisal template. After clicking on the tab for Predefined appraisal process in IMG node, you will follow the number of screens in sequece.
Excellent material is available on SAP Servicemarketplace for Performance Appraisal in EHP4. Please check the link below:
https://websmp109.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000687484&
Thanks!
Best Regards,
Chetan

Problem in running Process flow

Hi,
I’m bit new to OWB. I made mapping which I deployed successfully. I can run through control center and it works fine (it just fills a table). However when I made the process through process flow and after its validation , tries to start it gives me error RTC-5170: The selected objects do not require deployment as they are all up to date in the Control Center, which is followed by RTC-5006 and obviously no data generated in the table. How can I pass this error? Secondly I tried to schedule this, firstly it doesnot ask for the process flow during schedule, secondly even from schedule the map doesnot run.
Appreciate any help to run the process flow.
Regards
Yasir

In the process flow validate and generate the process flow. then go back to design center and go one step above to process flow package module and right click and deploy the process flow package. once the deployment is successfull then go back to the process flow and right click and start the process flow.
This should work.

OWB 11g Problem in running Process flow

I’ve build a process flow as described in “Getting Started with Oracle Warehouse Builder 11g”. But if I run the process flow I get a warning message “You have to deploy this object before running” followed by the error RTC-5170: The selected objects do not require deployment as they are all up to date in the Control Center.
Therefore I’m not able to run the process flow. What’s wrong? It looks so easy in Getting Started but it doesn’t work.
I’ve found two threads regarding this error from last year in this forum. But there is no solution for OWB 11g.
Has anyone an advice for me?

I've successfully installed OWF as described in Installation guide (all components are on the sam server).
But when I deploy a workflow in OWB I get some errors. In the job details
I find ORA-00942 and RPE-02053. It seems that the workflow repository is missing.
Are there additional steps for creating a workflow repository?
Or what is wrong? All installation logs (wf.log and workflow.log) are without errors and with success messages.
Any idea?

Process flow Condition Help

Thanks in Advance
I have a process flow like below
I have Function(out parameter) --> Returning 0 and 1
I have 2 mappings
1) Map1
2) Map2
What i need is
If function returns 0 i want to run MAP1
If function returns 1 i want to run MAP2
I my process flow what i did is
Start--> function --> Map1 --> Success
--> Map2 --> Success
After Function I added the complex condition(RTN_CODE = 0) for Map1
I added the complex condition(RTN_CODE = 1) for Map2
I am getting error VLD-10028: An activity having an outgoing transition with a complex condition must have another unconditional outgoing transition
If function returns 0 i want to run MAP1

Hi,
if you use conditional transitions you need one conditional transitions for each possible condition outcome or one transition without any condition that is used when none of the other conditions is met.
So you have to handle the case that the return value of your function is neither 0 or 1. Just add a transition without condition an connect it to the "end with errors" operator. This path will never be used if you make sure your function only returns 0 or 1. It is just required to validate the process flow.
Regards,
Carsten.

Where is a process flow's Execution details - Log section stored ?

Hi,
We're using OWB 11.2.0.1.7.
I want to know where in the database the Execution Details for a process flow is stored.
When i run a process flow with a Java Activity, or a User Defined Activity, and it halts with an Error i can inspect what went wrong in the process flow by opening the job in the Control Center client.
I doubleclick on the name of the job in the Control Center, the Job Details window opens.
I click on the first node, that is the name of the Job(process flow).
Then you click on the blue I aka 'Display Details'.
That window has a tab called Log.
The Log tab shows information that Java/Userdefined activity returns.
(In my case return info from a javabased xmlparser, or exitinfo from a shell command.)
This is the only place where i can find this info unfortunately.
I want to know where this info is stored in the database. I tried the runtime audit vews such as:
select e.*, m.*, l.*
from owbsys.wb_rtv_audit_executions e
LEFT JOIN owbsys.wb_rtv_audit_messages m ON e.audit_execution_id = m.audit_execution_id
LEFT JOIN owbsys.wb_rtv_audit_message_lines l ON l.audit_message_id = m.audit_message_id
left join owbsys.wb_rtv_audit_message_params p on p.audit_message_line_id = l.audit_message_line_id
But although i can see my processflow i can not find the Log information here.
Can someone tell me where this info is stored ?
Edited by: MichaelR64 on 6-apr-2011 14:01

Hi Michael
The standard output and error streams for the Java activities are stored in
-> ALL_RT_AUDIT_EXEC_FILES
Is this what you are after?
You can see the doc for it in the runtime public views section;
http://download.oracle.com/docs/cd/E11882_01/owb.112/e10584/api_2runviews.htm#i707034
The FILE_TYPE column will be set ot JavaErrorStream for example, with the information that was written to the Java std error stream, and JavaOutputStream will have the Java std output stream. This same technique is used for other activities - SQLPlus, SQLLoader, FTP.
Cheers
David

IStore process flows, where?

Where can I found a complete documentation of all process flows in iStore? We need this in a project where the customer needs to customize some flows. Please note that I have found some flows in the iStore 11i Concepts and Procedures (August 2000) but the doc set is not complete.

www-apps.us.oracle.com/ibe

PPT on SD process flow

Hi guys am in need of help from u
am not so clear about the SD process flow
can anyone pls send me a PPT on SD process flow
to my email id:- (<REMOVED BY MODERATOR>).
thanking u in advance..
Regards
Jino.

Sales Organization   :
Responsible for:
     Distribution of goods and services
     Negotiating Sales Conditions
     Product Liability and rights of recourse
     A sales organization is uniquely assigned to a company code
     Master datas are separately maintained for a sales organization
     All items in the Sales and Distribution document belong to a sales organization
Distribution Channel:
Means through which products and services reach the customer
A distribution channel:
     Defines responsibilities
     Helps in achieve flexible pricing
     Differentiate Sales statistics
Division:
     A division is used to group products and services.
     A division represents a product line.
Sales Area:
A Sales area is a combination of
     Sales organization
     Distribution Channel
     Division
Each Sales and distribution document is assigned exactly to one sales area.
A sales area can belong to only one company code.
     Sales Organization
     Distribution Channel
     Division
                 Sales Area
Plant and Storage Location:
     A Plant is a location where stock is maintained
     Plant and storage location are used by all logistic area of R/3 System
     A Plant is uniquely assigned to a company code
Shipping point:
     Shipping point is the highest level of organizational unit in shipping
     Each outbound delivery is processed by one shipping point
     Shipping points are assigned to a plant
     More than one shipping point can be assigned to a plant
Sales and Distribution is SAP begins with establishing customer relationship and ends with invoicing for the delivery of goods or service provided to the customer .
A Standard sales transaction has the following flow:
Inquiry
Quotation
Order
Delivery
Billing
The customer order management cycle begins with pre-sales activities.
A standard order in SAP contains:
     Customer and material info
     Pricing conditions
     Delivery dates and quantities
     Shipping info
     Billing Info
Inventory sourcing in SAP is taken care by
     Availability check
Shipping in SAP supports
     Outbound delivery creation
     Picking
     Packing
     Post Goods Issue
Billing in SAP supports
     Creating invoices for products and services
     Creating credit and debit memo
     Cancel previously posted billing documents
     Automatically transferring billing documents to accounting
When a billing document is created for a sales order we
     Credit the sales revenue account
     Debit the customer receivables account
Sales Document
A sales document is grouped into three structures
     Header
     Item
     Schedule Line
Outbound delivery
A delivery document is grouped into two structures
     Header
     Item
Several orders can be grouped into same outbound delivery if they have same
     Shipping point
     Delivery date
     Ship-to- address
Picking
     A transfer order is created for an outbound delivery
     A transfer order is created for a warehouse number
Post Goods Issue
When PGI is done the system
     Updates the quantity in inventory management and delivery requirements in materials planning
     Generates additional documents for accounting
     Adds the delivery to the billing due list
     Updates status in sales documents
Billing
We can group deliveries into single billing document if the deliveries have same
     Billing date
     Payer
     Destination Country
The effects of billing are
     Debit on the customer receivables account and credit on sales revenue account is created
     Sales information system
     Sales statistics is updated
Master data in SAP
SAP SD has got the following main masters:
     Customer master
     Material master
     Condition master
     Output master
     Customer material information master
Customer master
General Data                                         Sales Area Data          Company Code data
Tab pages                                              Tab pages                                      Tab pages
Address     Order             Accounting
Control data                                              Shipping               Payment
Payment terms                                          Billing               Correspondence
Marketing                                                   Partner functions                Insurance
Unloading points
Export data
Contact persons
The chart above shows detail on three main areas of customer master and the tab pages found under each area.
Material Master is maintained in different views and important views of sales and distribution are
     Basic data 1
     Sales Org 1
     Sales Org 2
     Sales : Gen/Plant
     Foreign Trade
     Sales text
Sales document in Sales and distribution mainly controls:
     Number range
     Item No increment
     Reference mandatory
     Item division
     Read info record
     Document pricing procedure
     Incomplete messages
     Alternative sales documents
     Delivery block
     Billing block
     Immediate delivery
     Delivery type
     Billing type
     Proposed delivery date
     Lead time for delivery
     Proposed pricing date
Plant determination in Sales and distribution:
To determine the plant in an order the system checks the master in the following order:
a)     Customer material info. record of the sold-to party
b)     Customer master record of the ship-to-party
c)     Material master record of the material
Shipping point determination
The following rule is used in determining shipping point in a sales order   :
Plant + Shipping condition (Sold-to-Party) + Loading group                  Shipping point
                                                      Maintained in Material master Gen: Plant data
Route determination
Route determined using the following rule in Sales and Distribution (SAP)
Departure Zone of Shipping Point
+
Shipping condition (Sold-to-Party)
+
Transportation Group (Material master)
+
Transportation Zone (Ship-to-Party)
Route
Delivery scheduling:
As name denotes delivery scheduling is scheduling delivery for an order and it carries the following important dates:
     Material availability date
     Transportation planning date
     Loading date
     Goods Issue date
     Delivery date
Availability Check in SAP:
     Availability check is carried out at item level for a plant
     Availability check is done on the material availability date
     If material availability date is in the past the forward scheduling is done, if not backward scheduling is done.
Item category determination in the order:
Item category denotes the category to which the item belongs and the following rule is used for determination of item category. Item category controls the way in which item behaves in a sales document.
Sales document type
+
Item category group (Material master)
+
Item usage
+
Item category of higher level item
Item category of the item
Item category in a sales document mainly controls the following
     Relevance for billing of an item
     Billing block
     Pricing relevance
     Business data relevance item
     Schedule line allowed
     Item relevant for delivery
     Returns
     Determine cost
     Credit active
     Incompletion procedure
     Partner determination procedure
     Structure scope (relevant for bill of material explosion)
     Value contract material
     Contract release control
Schedule line category:
Every item which has a delivery will have a schedule line and the schedule line category is determined with the following rule:
Item category + MRP type(Material Master)         Schedule line category
Schedule line category mainly controls:
     Delivery Block
     Movement type
     Item relevant for delivery
     Req/Assembly
     Availability
     Product Allocation
Copy Control:
Copy control is normally set for
     Header
     Item
     Schedule line levels
To control copying procedure we have
     Data transfer routines
     Copying requirements
     Switches
Pricing Procedure determination:
Pricing is an important component in SAP-SD. Once an order is entered taking into consideration some major factors, the pricing procedure for the particular order is determined.
The major factors taken into consideration for pricing procedure determination is:
Sales area
+
Customer Pricing procedure(Customer Master Sales area data)
+
Document Pricing Procedure(Sales Document Type)
Pricing Procedure
What are the components of pricing procedure?
How is that a person should work on Pricing Procedure?
To start with first
Define a Condition table:
What is a condition table?
A table where the key fields are data combinations for which messages are triggered (and offered for processing).
For each data combination, there is a condition record in the table. The data part contains the actual message.
As mentioned above a condition table is a table which carries key fields for picking up the prices.
Define Access Sequences
The access sequence is a search strategy which the SAP System uses to search for condition records valid for a condition type.
For example, you can define for a price that the SAP System first searches for a customer-specific price and then for a price list price.
Recommendation
     If you define your own access sequences, the key should start with the letter Z since SAP reserves this letter for the standard system.
     Do not change access sequences contained in the standard SAP R/3 System.
Actions
1. Check to what extent you can use the access sequences contained in the standard SAP R/3 System.
2. Create new access sequences by copying a similar access sequence and changing it according to your needs. Specify an alphanumeric key which may have up to 4 digits and a textual description.
3. Maintain the accesses for the access sequence by specifying the condition tables in the desired sequence. With the sequence, you define the priority of the accesses. You can display combinations of key fields using possible entries.
4. Generating the accesses is no longer necessary as of 3.0, as this is carried out automatically. You can generate the accesses manually, if required, by choosing "Utilities".
Example
In pricing, you use a customer-material discount. The condition records you create are based on customer data from the document header and material data from each document item. The discount is only valid for 2% of your customers, however. Normally, this would mean that the system would needlessly search through every available item for 98% of your customers. In this case, pre step would improve system performance.
Define Condition Type
A characteristic of a condition. For example, in pricing, different condition types are used to distinguish between a discount that refers to a net price and a discount that refers to a gross price.
Price elements are represented in the SAP system by condition types. Price elements can be, for example, prices, surcharges, discounts, taxes or, freight, and are stored in the system in condition records.
You can, for example, define whether a discount is calculated as a percentage or a fixed amount using the condition type.
You specify an access sequence in every condition type. Thus, you define which fields the SAP system checks when searching for a valid condition record.
Note
     The pricing procedure groups all condition types together which the SAP system is to automatically take into account during pricing for a business transaction (see the section "Define and assign pricing procedures").
Remember that you can only specify manually in a document those condition types which are contained in the pricing procedure.
     You can change the outcome of pricing in the sales document manually. You can limit options for changing a condition type in this IMG step.
Recommendation
     If you define your own condition types, the key should start with the letter Z since SAP reserves these letters for that purpose in the standard system.
     Do not change the condition types which are contained in the standard SAP R/3 System.
Actions
1. Check to what extent you can use the condition types contained in the standard SAP R/3 System.
2. Create new condition types by copying a similar conditions type and changing it according to your requirements. One reason for creating a new condition type is you may require a calculation rule for a discount which is not available in the standard system.
Specify an alphanumeric key which can have up to 4 digits, and a textual description.
Specify an access sequence for the condition types. You do not need to specify an access sequence for header conditions.
3. Maintain the detail screen of the condition type.
You can also assign a reference condition type if the condition types you are working with are similar. Then you will only have to maintain condition records for the reference condition type.
In addition, you can define the upper and lower limits for the value of a condition at condition type level. This way, you limit the amounts or the scale values in the corresponding condition records.
Define Pricing Procedures
The pricing procedure defines the conditions permitted for a document and the sequence in which the system takes these conditions into account during pricing.
A standard pricing procedure is defined in the standard SAP system. It contains conditions most commonly used. These include material prices, discounts, and surcharges, such as freight, or tax.
SAP Recommendation
     Define your own pricing procedures which contain only those condition types which you use. Otherwise, the system makes un neccessary accesses to conditions.
     Do not change the pricing procedures contained in the standard SAP R/3 System.
Actions
1. Create new pricing procedures by copying a similar pricing procedure.
o     Specify a key with up to 6 characters and a description.
o     For a procedure, specify the condition types in the sequence of their usage.
Maintain the lines of the pricing procedure
2. Afterwards define the customer determination procedures for determining the procedure.
3. Define the document pricing procedures for determining the procedure.
4. Assign the procedure to the sales document types and billing types.
5. To determine the procedure, define the allowed combinations of:
o     Sales area
o     Customer pricing procedure
o     Document pricing procedure
o     Pricing procedure
Shipping:
The basis for shipping is delivery.
Delivery document controls the following in deliveries
     Number range
     Item no increment
     Storage location rule
     Route determination
     Text determination
     Delivery split
     Gen. packing material / item
     Order required
Delivery item category controls:
     Check min delivery
     Availability check
     Relevant for picking
     Storage location required
     Determine storage location
     Automatic batch determination
     Text determination procedure
Billing:
Billing is the last phase in the SD process .Billing is the phase where the major integration of SD and FI Module happens.
Billing document has got the following structure:
     Header
     Item
Billing documents mainly control:
     No. range
     Posting block (Controls posting to accounting)
     Relevant for rebate
     Account determination procedure
     Account determination recon account
     Account determination pay.cards
     Output determination procedure
Account Determination in SAP
Account determination in SAP-SD happens with the following rule
Sales Organization
Chart of Accounts
Account assignment group Customer
Account assignment group-Material
Account Key
G/L account on which the postings has to happen.
CHeers!!!

SD Process Flow

Hi,
Can someone please provide a link/material for SD Process Flow, i,e. the Business Process involved in SD
Thanks,
Chinnu

hi
PO and SO
==========================================
Data Flow
     Master Data
     Sales Support
     Sales
     Shipping
     Billing
     Credit Management
     Foreign Trade / Customs
     Sales Information System
Master Data
     Business Partner / Customer
     Products
     Conditions
     Agreements / Contracts
     Terms of Payment
     Incoterms
     Routes
Sales Support
     Sales Promotions
     Sales Activities
     Potential Analysis
Sales
     Inquiry
     Quotation
     Order / Contract / Backorder
     Product Proposals
Shipping and Transportation
     Outbound Delivery
     Picking
     Packing
     Loading
     Shipment
     Post Goods Issue
     Billing
Billing
     Billing
Credit Management
Foreign Trade / Customs
Sales Information System
Activities Involved by the SAP SD End User
     Inquiry Processing
     Quotation Processing
     Contract Processing
     Sales Order Processing
     Scheduling Agreement Processing
     Returns Processing
     Rebate Processing
     Sales Deal and Promotion Processing
     Display Customer and Material Information
     Billing Processing (online)
     Billing Processing (In The Background)
     Invoice List Processing
     Maintain Customer and Material Information
     Display Pricing
     Maintain Pricing
     Release Blocked Documents for Billing
     Release Sales Orders for Delivery
     Display Sales Information
     Display Billing Documents
     Sales Analysis
     Credit Management in Sales and Distribution Documents
     Backorder Processing
     Sales Support
     Output Processing
Inquiry Processing
     Create/change/display inquiries
     Generate lists for inquiries and incomplete inquiries
     Select sales documents according to object status
Quotation Processing
     Create/change/display quotations
     Generate lists for quotations and incomplete quotations
     Select sales documents according to object status
Contract Processing
     Create/change/display contracts
     Generate and process list of contracts
     Generate and process list of incomplete contracts
     Select sales documents according to object status
Sales Order Processing
     Create/change/display sales orders
     Generate and process list of sales orders
     Generate and process list of incomplete sales orders
     Select and process sales documents according to object status
     Select and process sales documents in a period of time
     Select and process duplicate sales documents in a period of time
Scheduling Agreement Processing
     Scheduling agreement processing
     Select and process incomplete scheduling agreements
     Select sales documents according to object status
Returns Processing
     Create/change/display sales orders
     Create/change outbound delivery
Rebate Processing
Rebate processing:
     Maintain rebate agreements
     Extend rebate agreement
     Settlement of rebate agreements
     Generate list of rebate agreements
Billing document:
     Display billing document
     Compare the rebate basis from billing documents and statistics
     Update billing documents referring to rebate conditions
Sales Deal and Promotion Processing
     Create/change/display sales deals
     Generate list of sales deals
     Create/change/display promotions
     Generate list of promotions
Display Customer and Material Information
     Display customer (Sales)
     Display material
     Display material listing/exclusion
     Select customer material info record according to customer
     Select customer material info record according to material
     Display customer hierarchy
     Display sales deals
     Display promotions
     Display rebate agreements
     Display cross selling materials
     Display assortment module for value contracts
Billing Processing (online)
     Create/change/display billing document
     Cancel billing document
     Retroactive billing
     Process billing due list
     Set billing date
     Display billing documents from the archive
     List of billing documents
     Rebook accounting indicator
     Release sales orders for billing
     Display sales and distribution documents blocked for billing
Billing Processing (In the Background)
     Display billing document
     Generate batch jobs for billing
     Generate log for billing document run
Invoice List Processing
There are two types of invoice lists in the Standard:
1.     one for invoices and debit memos
2.     one for credit memos
     Create/change/display invoice lists
     Process work list for invoice lists
     Generate invoice list
     Generate cancellation invoice list
     Display invoice list from the archive
Maintain Customer and Material Information
     Maintain material listing/exclusion
     Reference material listing/exclusion
     Maintain material substitution
     Reference material substitution
     Maintain material information
     Select customer material information according to material or customer
     Maintain material
     Maintain customer (Sales)
     Maintain customer hierarchy
     Maintain materials for cross selling
     Maintain value contracts
     Maintain Incoterms
Display Pricing
     Display condition records
     Display condition lists
     Display conditions using index
     Display free goods determination
Maintain Pricing
     Create/change/display condition
     Condition processing using index
     Create/change/display free good
     Create/change/display condition lists
     Process net price list
     Release expected customer price
Release Blocked Documents for Billing
     Release sales orders for billing
     Change billing document
     List of blocked billing documents
Release Sales Orders for Delivery
     Change sales order
     Block and unblock customer from sales view
     Generate lists for incomplete sales documents and for sales documents blocked for delivery
Display Sales Information
     Generate list for quotations, contracts, sales orders or scheduling agreements
     Generate list for incomplete quotations, contracts, sales orders or scheduling agreements
     Generate list of sales orders blocked for delivery
     Display sales activities, item proposals, material listing and material exclusion
     Sales support monitor
Display Billing Documents
     Display billing document
     Display list of billing documents
     Display blocked billing documents
Sales Analysis
     Contracts: Lists for overdue and completed contracts
     Quotations: Lists for overdue and completed quotations
     Backorder processing: Backlog list, selection list
     Generate list for: Inquiries, rebate agreements, scheduling agreements
     Information on the customer: Sales summary, list of top customer
     Material information: List of top materials
     Sales support monitor
     Flexible planning: Display/create/change
Credit Management in Sales and Distribution Documents
     Process credit authorization for sales and distribution documents
     List of released sales and distribution documents
     List of blocked sales and distribution documents
     Process credit authorization according to sales and distribution document
     Process credit authorization according to delivery
     List of incomplete sales and distribution documents
     Sales and distribution documents blocked for delivery
     Delivery monitor
     List of billing documents
Backorder Processing
     Display backlogged sales orders
     Process backorder processing using selection list according to sales documents
     Backorder processing: access using the material
     Execute rescheduling of sales documents
     Evaluate rescheduling of sales documents
Sales Support
     Create/change/display sales activities
     Executing mailing promotions
     Display and create interested parties and contact persons
     Display sales summary
     Sales support monitor
     Display competitive products
Output Processing
     Display/change/create output-condition records in Sales
Integration between SD and MM :-
1. When you create sales order in SD, all the details of the items are copied from Material master of MM.
2. MRP and availability check related data is also taken from MM although you control this data in SD also.
3. While you create inbound/outbound delivery with reference to a sales order,the shipping point determination takes place with the help of the loading group, plant data, shipping conditions etc. This also refers to Material Master.
4. The material which you are entering in a sales order must be extended to the sales area of your sales order/customer otherwise you cannot transact with this material.
Integration between SD and FI :-
1. Whenever you create a delivery with reference to a sales order, goods movement takes place in the background. eg. In case of standard sales order, you create an outbound goods delivery to the customer. Here movement 601 takes place. This movement is configured in MM. Also, this movement hits some G/L account in FI. Every such movement of good s hits some G/L account.
2. The accounts posting in FI is done with reference to the billing documents (invoice, debit note, credit note etc) created in SD. Thus this is a link between SD and FI
3. Tax determination: In case of a tax determination also, there is a direct link between SD and MM
Different areas where SD is Integrated
Sales Order
Availability Check                      -       MM
Credit Check                             -       FI
Costing                                  -       CO/ MM
Tax Determination                   -       FI
Transfer of Requirements            -       PP/ MM
Delivery & Goods Issue
Availability Check                  -       MM
Credit Check                             -       FI
Reduces stock                       -       MM
Reduces Inventory $                 -       FI/ CO
Requirement Eliminated              -       PP/ MM
Billing -
Debit A/R                                -       FI/ CO
Credit Revenue                      -       FI/ CO
Updates G/ L                        -       FI/ CO
(Tax, discounts, surcharges
Milestone Billing                        -       PS
Return Delivery & Credit Memo -
Increases Inventory                 -       MM
Updates G/ L                        -       FI
Credit Memo                         -       FI
Adjustment to A/R                   -       FI
Reduces Revenue                     -       FI
Reward if USeful
Thanx .. Naren..
Message was edited by:
        Dasari Narendra

Standard Appraisal process

Hi
I've created the Competency, Assessment template and appraisal template
I also created a sample Questionnaire
Now i am not able to figure out the process the manager to initiate the Appraisal so it will go to the employee and where employee can fill it up and submit it back to manager. Once this is done it has to flow to the HR department
Can anyone guide me in the appraisal process and also let me know if i've missed any setup
Any metalink note for the appraisal would also be really great
Thanks for the time
Regards
Ramesh Kumar S

You should be able to begin the appraisal process from the manager. The workflow will take you to a point where you can transfer it back to the employee to update.
The approaisal workflow is more complex than most, because it allows for transferring the appraisal backwards and forwards between participants.
If there is a final approver after the manageer, then AME is a good way of controlling this.
Regards
Tim

PMS Appraisal Process

Dear Experts,
If you have any configuration documents on PMS Appraisal,pls do let me know.
because i dont have much idea on appraisal process.
Client would like to implement the entire end to end process.
Pls do help me.
Edited by: sivakpt on May 3, 2011 2:06 PM

HI,
Go to ooam transaction where you have to define the appraisal template there you have to configure every thing like work flow process, any new enhancement and before implementing appraisal process study entire your client process then you implement
and go to basic setting and configure your settings
Let me tell you few transaction code
Appcreate- here you can create the appraisal template
appdelete - Here u can delete
appsearch - here u can know the status of the process
Regards,
prasath
Edited by: SN Vijay Rajandra Prasath on May 3, 2011 2:08 PM
Edited by: SN Vijay Rajandra Prasath on May 3, 2011 2:09 PM

To check whether a process flow is valid or not

Hi,
I want to check whether a OWB process flow is valid or not inside a PL/SQL block. Can anyone let me know about any repository table or view where I can check the process flow status.
Regards,
Poulose

Use display schedule job option from the context menu of the start variant of the process chain.
When u chick this.. u will get the available job on this start process.. There u can see whether the process chain in schedule mode or not?
If u can see multiple schedule then u can delete the older ones which are not needed and then u can maintain only one schedule job.
If u click twice.. then there are chances that u might end up with the 2 schedule job with the same time frame.. .. so check the same with the steps mentioned..... if u find two jobs then u need to delete one.. if not there might be chance that ur PC might get trigger twice.. and one trigger will gets failed. and the other one will gets executed..
Thanks
I hope this is clear to u..
Assign points if this helps

Training and Event management.Process Flow..

Hi, Experts,
Can any body give me some notes on Training and event management and process flow also like integration between ECC-6.0 to Non SAP
1.Training request
2.Appraisal documents for performance feedback
3.Tracking Feedback processes
Pls help me in configuring these services.
With Regards,
San Rao.

Hi san rao,
as per your reply you using the new appraisal template and also you have released the template now simply run the BSP application HAP_DOCUMENT and access the appraisal documents
attach these BSP applications in your portal system.
following pages of the above application will be help full
documents_todo
documents_received_open2
documents_where_participated
Regards,
Umesh Chaudhari.

Flexible Appraisal Process Flow EHP-7, Where to start???

Similar Messages

Maybe you are looking for