Process flow - Integrating all modules

Hi All
I have been working in SAP BI for the last 4 years. I want to gain a integrated perspective of the process flow in SAP. It would help me if someone can pass on any document which outlines the big picture. How things flow and are integrated between modules?
I would also want to understand how I can expand my base in SAP. What are the other modules that I can pick up?
Thanks

Check my weblog and you will get some idea
SAP Netweaver - BPM & SOA Enabler
Also an example scenario at my wiki
https://wiki.sdn.sap.com/wiki/display/BPX/LeaveApprovalSecnariowithNetWeaver+7.1
Regards,
Prateek

Similar Messages

CRM modules - Process questionnaires, Process flows

Can any one help find where I can access process questionnaires(RD 20),Process flows for CRM modules Telesales, sales support, I marketing, I store and service contracts. I need them for my present assignement. Any help would be highly appreciated.If you have any previous documentation please send them to [email protected] I would be very helpful to you.

Hi,
Refer the links,
[Explanation of the Process Flow|http://www.sapdb.org/7.4/htmhelp/dc/043d57ed2b11d4aa9a006094b92fad/content.htm]
[SAP MM Process Flow-1|http://www.saptechies.com/mm-process-flow/]
[SAP MM Process Flow-2|http://www.sapbrainsonline.com/sapinfo/tutorial.php?artid=582]
Regards,
Shyamal

QM process flow

Hi,
Can any one explain the general process flow of Qm module.I have no idea on the Qm management.
Thanks.
-Santhosh

Dear Santhosh,
In Quality Management following are the broad level activities need to be conducted :
1) Incoming Inspection : This is for raw materials, or other input materials on which the quality of final product is dependent. (For activating this, in QM material master you need to define '01' inspection type)
2) In process Inspection : This is the inspection in - process meaning in house inspection during the process inside. (For activating this, in QM material master you need to activate '03' inspection type)
3) Final Inspection or out going inspection : This is inspection of final products or finished product. This is to ensure that correct quality product is going to customer. (For activating this, in QM material master you need to activate '04' inspection type)
Apart from this you can do inspections at vendor, predespatch insp, Recurring insp ,competitors sample evaluation etc.
For doing all this in terms of SAP you need to do:
1) Quality Planning : Defining of masters like Master Inspection characteristics, Inspection method, sampling scheme, sampling procedure, catalog selected sets and code groups, then assign all these Masters in Inspection Plan . also assigning QM view to materiel master so that inspections are activated.
2) Quality Inspection : Inspection lot creation , result recording, defect recording and completing the lot by giving user decesion.
3) Quality control : This include raising notification, SPC, using dynamic modification, quality certificates etc.
4) Test equipment management : This includes Calibration of instruments
5) Control in logistics : This include Control in Procurement, Production and sales & distribution
you can get all details of these processes at
http://help.sap.com/saphelp_erp60_sp/helpdata/en/a6/df293581dc1f79e10000009b38f88/frameset.htm
Best Regards,
Shekhar

How to schedule mappings to process flows?

Hi,
I have shceduled a calendar (Job) which is referring to a process flow. But how can I make sure that the mappings are referring to the same process flow?
E.g. I have scheduled job at 10 AM , I have created the process flow for 10 AM referring to the same scheduled job.
My understanding here is there is a hierarchy : Scheduled jobs > Process Flows > Mappings
I have configured the process flow to run it at a scheduled job, now I want the mappings to understand to run at the same time as that of the schedule.
And also when I start the process flow all the mappings should get executed.
Is there any parameter to tell the process flow that all these mappings falls under you.
Hope I have made myself clear.
Can anyone please look into this query?
Thnks in adv..

When I double click and open my process flow I am not able to see any mapping. We have stored procedures written:
ln_exists NUMBER;
LS_ERROR VARCHAR2(200);
LD_START_PERIOD_DT DATE;
LD_END_PERIOD_DT DATE;
EX_PF_NOT_VALID EXCEPTION ;
EX_SUB_PF_NOT_VALID EXCEPTION ;
EX_LAYER_NOT_VALID EXCEPTION ;
EX_MODULE_NOT_VALID EXCEPTION ;
EX_DATE_FORMAT_ERR EXCEPTION ;
BEGIN
--1: Check the Process Flow parameter value
IF IP_PF IS NOT NULL THEN
select count(*)
into ln_exists
from adm_process_flow_par
where process_flow = IP_PF;
IF ln_exists =0 THEN
RAISE EX_PF_NOT_VALID;
END IF;
END IF;
--2: Check Sub Process Flow Parameters value
IF IP_SUB_PF IS NOT NULL THEN
select count(*)
into ln_exists
from adm_sub_pf_par
where sub_pf_code = IP_SUB_PF;
IF ln_exists = 0 then
RAISE EX_SUB_PF_NOT_VALID;
END IF;
END IF;
--3:Check Layer Code Parameter Value
IF IP_LAYER IS NOT NULL THEN
select count(*)
into ln_exists
from adm_lookup_code
where lookup_type='LAYER_CODE'
and lookup_code= IP_LAYER;
IF LN_EXISTS =0 THEN
RAISE EX_LAYER_NOT_VALID;
END IF;
END IF;
--4: Check Module Code Parmeter Value
IF IP_MODULE IS NOT NULL THEN
select count(*)
into ln_exists
from adm_lookup_code
where lookup_type IN ('SOURCE_SYSTEM','SUBJECT_CODE')
and lookup_code= IP_MODULE;
IF LN_EXISTS =0 THEN
RAISE EX_MODULE_NOT_VALID;
END IF;
END IF;
--5: Check start Period date & End Period Date Format
BEGIN
IF IP_START_PERIOD_DT IS NOT NULL THEN
LD_START_PERIOD_DT := TO_DATE(IP_START_PERIOD_DT,'YYYY-MM-DD');
END IF;
IF IP_END_PERIOD_DT IS NOT NULL THEN
LD_END_PERIOD_DT := TO_DATE(IP_END_PERIOD_DT,'YYYY-MM-DD');
END IF;
EXCEPTION
WHEN OTHERS THEN
RAISE EX_DATE_FORMAT_ERR;
END;
EXCEPTION
WHEN EX_DATE_FORMAT_ERR THEN
LS_ERROR := 'Date Format is not valid ,please check (FORMAT: YYYY-MM-DD HH24 /YYYYMMDDHH24)';
SP_ERROR_REC(NULL,IP_PF,IP_SUB_PF,IP_MODULE,IP_LAYER,NULL,NULL,LS_ERROR,'SP_CHECK_PARAMETER_VALID',NULL);
RAISE_APPLICATION_ERROR(-20002,LS_ERROR);
WHEN EX_PF_NOT_VALID THEN
LS_ERROR := 'The Process Flow Value is not valid ,please check table adm_process_flow_par';
SP_ERROR_REC(NULL,IP_PF,IP_SUB_PF,IP_MODULE,IP_LAYER,NULL,NULL,LS_ERROR,'SP_CHECK_PARAMETER_VALID',NULL);
RAISE_APPLICATION_ERROR(-20002,LS_ERROR);
WHEN EX_SUB_PF_NOT_VALID THEN
LS_ERROR := 'The Sub Process Flow Value is not valid ,please check table adm_sub_pf_par';
SP_ERROR_REC(NULL,IP_PF,IP_SUB_PF,IP_MODULE,IP_LAYER,NULL,NULL,LS_ERROR,'SP_CHECK_PARAMETER_VALID',NULL);
RAISE_APPLICATION_ERROR(-20003,LS_ERROR);
WHEN EX_LAYER_NOT_VALID THEN
LS_ERROR := 'The Layer Code Value is not valid ,please check adm_lookup_code(lookup_type="LAYER_CODE")';
SP_ERROR_REC(NULL,IP_PF,IP_SUB_PF,IP_MODULE,IP_LAYER,NULL,NULL,LS_ERROR,'SP_CHECK_PARAMETER_VALID',NULL);
RAISE_APPLICATION_ERROR(-20004,LS_ERROR);
WHEN EX_MODULE_NOT_VALID THEN
LS_ERROR := 'The Layer Code Value is not valid ,please check adm_lookup_code(lookup_type IN ("SOURCE_SYSTEM","SUBJECT_CODE")';
SP_ERROR_REC(NULL,IP_PF,IP_SUB_PF,IP_MODULE,IP_LAYER,NULL,NULL,LS_ERROR,'SP_CHECK_PARAMETER_VALID',NULL);
RAISE_APPLICATION_ERROR(-20005,LS_ERROR);
END;
Can anyone throw some light on this issue?
Edited by: user11001347 on May 11, 2010 11:46 PM

Design for process flow in OWB

Hi Experts
I want to design my process flow. Please send the processflow design template/Document.
Regards
frnd

You define an Oracle Workflow location to specify where you want to deploy your process flows. The Oracle Workflow location points to a workflow schema that runs in the target database. Warehouse Builder process flows comply with the XML Process Definition Language (XPDL). When you generate a process flow, Warehouse Builder generates an XML file in the XPDL format. You can plug the generated XML file into any workflow engine that follows the XPDL standard.
Process Flow Modules include Process Flow Packages that include Process Flows. The Process Flow Package is a grouping mechanism that determines which process flows you can interrelate. At run time, you can launch one process flow that launches other Process Flows that exist in the same process flow package.
The Process Flow Module acts as a container by which you can validate, generate, and deploy a group of Process Flows.
So, it concludes that there is no standard design for process flows, it all depends to your datawarehouse and your ETL process(extracting, transformning. loading)

RPE-01008: Recovery of this request is in progress in process flows.

Hi,
I am calling shell script as an userdefined activity in a process flows.
All the process flows were working fine.
Today, all the process flows wherever the shell script is called ended up with an error showing " RPE-01008: Recovery of this request is in progress".
Could any one please explain, what might be reason?
Thanks in advance.
Thank you,
Regards,
Gowtham Sen.

Hi,
we have exactly the same problem here.
Does anybody have a solution?
regards
Lutz

Process flow - Active Directory integration with Enterprise Portal

Hi
I have seen number of documents/forum discussions on integrating Microsoft Active Directory (LDAP) with Enterprise Portal, but unable to find out the process flow for achieving the same.
I have installed Enterprise Portal 6 (SP13) running on Web AS 640 (J2EE Standalone). The UME is currently configured to use Java database. (i.e datasourceconfiguration_database_only.xml)
I intend to proceed as below for integrating with Active Directory and integrate with Windows authentication:
1) Configure UME to use an LDAP Server as Data Source using Config Tool
http://help.sap.com/saphelp_erp2004/helpdata/en/cc/cdd93f130f9115e10000000a155106/frameset.htm
2) Configure Enterprise Portal UME i.e http://<host name>:50000/irj - System Administration - System Configuration - UM Configuration
<b>Should I configure Data Sources & LDAP Server here as I have already configured these using J2EE Config tool (point no.1).</b>
3) Integrate Windows authentication with EP using IISProxy module.
I hope the above will enable me to logon to Portal without supplying username and password once you are logged on to the PC using your Windows user name and password.
Also, any schema updates required to Activie Directory i.e What additional data is stored in A.D.
I would appreciate your guidance on this.
Thanks in advance,
Chandu

Hi Chandau,
you wanted that some users are not taken into account by the User Management Engine (UME).
This behavior can be established by specifying the
ume.ldap.negative_user_filter property for the LDAP data sources in the data source configuration file. Using this property one can define that all users and accounts that
match the defined conditions are filtered out by the UME API.
A detailed documentation can be found in the SAP Online Help:
http://help.sap.com/saphelp_nw04/helpdata/en/9a/f43541b9cc4c0de10000000a1550b0/
content.htm
In the following example of a data source configuration file for Microsoft Active Directory
Server the attribute userPrincipalName is used as Logon ID of a portal user id (j_user).
Here the user accounts that have one of the following Logon IDs (index_service,
notificator_service and cmadmin_service ) are filtered out.
<dataSources>
</dataSource>
<dataSource id="CORP_LDAP">
<privateSection>
<ume.ldap.negative_user_filter>
userPrincipalName=[index_service,notificator_service,cmadmin_service]
</ume.ldap.negative_user_filter>
</privateSection>
</dataSource>
</dataSources>

Integrating process flows

Hi All,
I had different projects in my OWB and each process has its process flow which has several mappings in it.
I want to integrate all of these process flows from different projects into a single process flow where I can either run two process flows parallel or one after another and should also be able to decide whether to continue or not if one process flow fails.
Can you please help me, Is it possible if not is their any work around for it.
Many Thanks,
Danish

For example, you have
Project P1
   Processflow module OWF1 with location name LOC_OWF1
   Processflow for this application P_PROJ1
Project P2
   Processflow module OWF2 with location name LOC_OWF2
   Processflow for this application P_PROJ2Under OWB (runtime) repository owner create procedure
create or replace procedure P_MASTER_PROCESS as
return_result1 NUMBER(10);
return_result2 NUMBER(10);
begin
return_result1 := WB_RT_API_EXEC.RUN_TASK(location=>'LOC_OWF1', task_type=>'PROCESSFLOW', task_name=>'P_PROJ1',
      system_params=>',', custom_params=>',', oem_friendly=>0, background=>0);
return_result2 := WB_RT_API_EXEC.RUN_TASK(location=>'LOC_OWF2', task_type=>'PROCESSFLOW', task_name=>'P_PROJ2',
      system_params=>',', custom_params=>',', oem_friendly=>0, background=>0);
end;Oleg
Message was edited by:
tsiboleg

Process flow for Maintenance Event Builder integrated with PS

Dear EAM Master ,
Good Day. Can anyone show me how's the process flow for Process flow for Maintenance Event Builder integrated with PS.
Appreciate.
Thank you.

[SAP Help|http://help.sap.com/erp2005_ehp_05/helpdata/en/d7/d0b83a47d0c649e10000000a114084/frameset.htm]
Thanks
Narasimhan

How to specify the Process Flow Module with SQLPLUS_EXEC_TEMPLATE.SQL ?

Hi, we have a couple of process flow modules that have PF Packages and Process Flows with the same name.
E.g
PFMOD1 (Module)
FILELOAD (Package)
PF1 (Pf)
PFMOD2 (Module)
FILELOAD (Package)
PF1 (Pf)
Normally we can specify "FILELOAD/PF1" as a paramater to the procedure SQLPLUS_EXEC_TEMPLATE.SQL in order to initiate the running of an OWB process flow but how can the system distinguish between modules ?
Anyone done this ?
Thanks
Paul

If you deployed the packages to the same location then the second deployment replaced the result of the first one (actually a new version of the process flow was created). You can execute only the latest version...
Regards,
Robert

Owb 11 deploy process flow module - Java Exception

I tried to deploy a process flow module (under the schema OWF_MGR). This is the error message:
java.lang.NullPointerException
java.lang.NullPointerException
at oracle.wh.ui.runtime.application.WHRuntimeCommandGenerateDeploy.getPreGenerationCandidateContexts(WHRuntimeCommandGenerateDeploy.java:3576)
at oracle.wh.ui.runtime.application.WHRuntimeCommandGenerateDeploy.doPreDeploymentActions(WHRuntimeCommandGenerateDeploy.java:3252)
at oracle.wh.ui.runtime.application.WHRuntimeCommandGenerateDeploy._internalDeploy(WHRuntimeCommandGenerateDeploy.java:2420)
at oracle.wh.ui.runtime.application.WHRuntimeCommandGenerateDeploy.doDeploymentAsynch(WHRuntimeCommandGenerateDeploy.java:2117)
at oracle.wh.ui.runtime.application.WHRuntimeCommandHandler$1.construct(WHRuntimeCommandHandler.java:1026)
at oracle.wh.ui.runtime.SwingWorker$2.run(SwingWorker.java:124)
at java.lang.Thread.run(Thread.java:595)
What is the problem?
Thanks,
Luca

Thanks! I tried the deployment of process from OMB Plus and it's work correctly.
Do you if exist a patch for the OWB 11 client?
Regards,
Luca

Audit browser showing complete for all process flows.

Hi,
My process flows are executing success fully.
Based upon the activities I am ending the process with END_SUCCESS, END_ERROR or END_WARNING acitivities.
But here even, the process flow is ended up with END_ERROR activitiy the process flow status is shown as 'Complete'. But its not showing the final status as "Error".
In the backend, in the audit tables its showing the return status as "Failure"
Could any one please explain me, how to show its status as fialure.
Thank you,
Regards,
Gowtham Sen.

Hi,
From your description, I know you do not want to close your browser when users sign out SharePoint 2013.
As you know, “the browser has to terminate the session and clear the cache.” You can customize your sign out page by referring to this article: https://controlzet.wordpress.com/2014/02/17/sharepoint-custom-sign-out-page/.
Best Regards
Vincent Han
TechNet Community Support

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

Error while creating Process flows in OWB 11gR2

Hi
I have never faced this before and thats why it baffles me. I am trying to create a new process flow module which has already been configured to the OWF_LOCATION(Oracle workflow location).
I get Java exception error window with long list of details which are rocket science to me.
I will paste few lines of the details as its a big trace
Internal Error: Load Error. Please contact Oracle Support with the stack trace and details on how to reproduce it.
Internal Error: Load Error. Please contact Oracle Support with the stack trace and details on how to reproduce it.
Persistent Layer Error:SQL Exception..
Class Name: ProxyFactory.
Method Name: loadInstance.
Persistent Layer Error Message: Exhausted Resultset.
     at oracle.wh.repos.impl.ProxyFactoryGen.loadInstance(ProxyFactoryGen.java:9704)
     at oracle.wh.repos.pdl.foundation.CacheMediator.query(CacheMediator.java:4372)
     at oracle.wh.repos.pdl.foundation.CacheMediator.queryById(CacheMediator.java:4221)
AND
     Trying to access invalid Object.
Element ID: 124688
Status: 15
Name: PFM_BUS_ROUTE
Logical Name: PFM_BUS_ROUTE
Class Name: CMPProcessInstalledModule
Owning FCO: 124688
parent:0
Trying to access invalid Object.
Element ID: 124688
Status: 15
Name: PFM_BUS_ROUTE
Logical Name: PFM_BUS_ROUTE
Class Name: CMPProcessInstalledModule
Owning FCO: 124688
parent:0
     at oracle.wh.repos.pdl.foundation.WBProxy.checkStatus(WBProxy.java:587)
     at oracle.wh.repos.pdl.foundation.WBProxy.getSubject(WBProxy.java:67)
     at oracle.wh.repos.pdl.foundation.WBProxy.getContext(WBProxy.java:132)
     at oracle.wh.ui.owbcommon.OWBWizardDefinition.produceRefresh(OWBWizardDefinition.java:934)
     at oracle.wh.ui.owbcommon.OWBWizard.wizardFinished(OWBWizard.java:1036)
This is really strange.Has anyone encountered this before?
Birdy

Hi David
I tried registering the location again before de-registering it. OWB comes up with an RTC error
RTC-5229: Location <Location Name> could not be unregistered.
Any hints?
Version details are below. I am not sure whether Critical patch refers to this
About
Oracle Warehouse Builder 11.2.0.2
OWB Tahoe Development Version 11.2.0.2
Build OWB_TAHOER2_LINUX_100907.2019.2.0.3
Copyright © 2000, 2010, Oracle and/or its affiliates. All rights reserved.
IDE Version: 11.1.1.0.30.51.07
Product ID: oracle.owb
Product Version: 11.2
Version
Component     Version
=========     =======
Java(TM) Platform     1.5.0_24-rev
Oracle IDE     11.2.0.2.0
Properties
Name     Value
====     =====
apple.laf.useScreenMenuBar     true
awt.toolkit     sun.awt.windows.WToolkit
class.load.environment     oracle.ide.boot.IdeClassLoadEnvironment
class.load.log.level     CONFIG
class.transfer     delegate
com.apple.macos.smallTabs     true
com.apple.mrj.application.apple.menu.about.name     "OWB"
com.apple.mrj.application.growbox.intrudes     false
file.encoding     Cp1252
file.encoding.pkg     sun.io
file.separator     \
ice.browser.forcegc     false
ice.pilots.html4.ignoreNonGenericFonts     true
ice.pilots.html4.tileOptThreshold     0
ide.AssertTracingDisabled     false
ide.bootstrap.start     2245311504606534
ide.build     OWB_TAHOER2_LINUX_100907.2019.2.0.3
ide.conf     C:\product\11.2.0\dbhome_2\owb\bin\owb.conf
ide.config_pathname     C:\product\11.2.0\dbhome_2\owb\bin\owb.conf
ide.debugbuild     false
ide.devbuild     false
ide.extension.search.path     owb/extensions:ide/extensions
ide.firstrun     false
ide.java.minversion     1.5.0
ide.launcherProcessId     4792
ide.main.class     oracle.ide.boot.IdeLauncher
ide.patches.dir     owb/lib/patches
ide.pref.dir     C:\Documents and Settings\bharadwajvenkatraman\Application Data\OWB
ide.pref.dir.base     C:\Documents and Settings\bharadwajvenkatraman\Application Data
ide.product     oracle.owb
ide.shell.enableFileTypeAssociation     C:\product\11.2.0\dbhome_2\owb\bin\owb.exe
ide.splash.screen     splash.gif
ide.startingArg0     C:\product\11.2.0\dbhome_2\owb\bin\owb.exe
ide.startingcwd     C:\product\11.2.0\dbhome_2\owb\bin
ide.user.dir     C:\Documents and Settings\bharadwajvenkatraman\Application Data\OWB
ide.user.dir.var     IDE_USER_DIR
ide.work.dir     U:\Data\OWB
ide.work.dir.base     U:\Data
java.awt.graphicsenv     sun.awt.Win32GraphicsEnvironment
java.awt.printerjob     sun.awt.windows.WPrinterJob
java.class.path     ..\lib\int\accelerators.jar;..\..\ide\lib\ide-boot.jar
java.class.version     49.0
java.endorsed.dirs     C:\product\11.2.0\dbhome_2\jdk\jre\lib\endorsed
java.ext.dirs     C:\product\11.2.0\dbhome_2\jdk\jre\lib\ext
java.home     C:\product\11.2.0\dbhome_2\jdk\jre
java.io.tmpdir     C:\DOCUME~1\BHARAD~1\LOCALS~1\Temp\
java.library.path     C:\product\11.2.0\dbhome_2\owb\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\product\11.2.0\dbhome_2\OPatch;C:\product\11.2.0\dbhome_2\bin;C:\OraHome_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Windows Imaging\;C:\Program Files\Open Text\Livelink Explorer\;C:\WINDOWS\system32\WindowsPowerShell\v1.0;C:\Program Files\Microsoft Application Virtualization Client
java.naming.factory.initial     oracle.javatools.jndi.LocalInitialContextFactory
java.runtime.name     Java(TM) Platform, Standard Edition for Business
java.runtime.version     1.5.0_24-rev-b08
java.specification.name     Java Platform API Specification
java.specification.vendor     Sun Microsystems Inc.
java.specification.version     1.5
java.util.logging.config.file     logging.conf
java.vendor     Sun Microsystems Inc.
java.vendor.url     http://java.sun.com/
java.vendor.url.bug     http://java.sun.com/cgi-bin/bugreport.cgi
java.version     1.5.0_24-rev
java.vm.info     mixed mode
java.vm.name     Java HotSpot(TM) Client VM
java.vm.specification.name     Java Virtual Machine Specification
java.vm.specification.vendor     Sun Microsystems Inc.
java.vm.specification.version     1.0
java.vm.vendor     Sun Microsystems Inc.
java.vm.version     1.5.0_24-rev-b08
line.separator     \r\n
native.canonicalization     false
oracle.home     C:\product\11.2.0\dbhome_2
oracle.ide.util.AddinPolicyUtils.OVERRIDE_FLAG     true
oracle.net.tns_admin     ../../network/admin
oracle.translated.locales     de,es,fr,it,ja,ko,pt_BR,zh_CN,zh_TW
oracle.xdkjava.compatibility.version     9.0.4
os.arch     x86
os.name     Windows XP
os.version     5.1
path.separator     ;
reserved_filenames     con,aux,prn,lpt1,lpt2,lpt3,lpt4,lpt5,lpt6,lpt7,lpt8,lpt9,com1,com2,com3,com4,com5,com6,com7,com8,com9,conin$,conout,conout$
sun.arch.data.model     32
sun.boot.class.path     C:\product\11.2.0\dbhome_2\jdk\jre\lib\rt.jar;C:\product\11.2.0\dbhome_2\jdk\jre\lib\i18n.jar;C:\product\11.2.0\dbhome_2\jdk\jre\lib\sunrsasign.jar;C:\product\11.2.0\dbhome_2\jdk\jre\lib\jsse.jar;C:\product\11.2.0\dbhome_2\jdk\jre\lib\jce.jar;C:\product\11.2.0\dbhome_2\jdk\jre\lib\charsets.jar;C:\product\11.2.0\dbhome_2\jdk\jre\classes
sun.boot.library.path     C:\product\11.2.0\dbhome_2\jdk\jre\bin
sun.cpu.endian     little
sun.cpu.isalist
sun.desktop     windows
sun.io.unicode.encoding     UnicodeLittle
sun.java2d.ddoffscreen     false
sun.jnu.encoding     Cp1252
sun.management.compiler     HotSpot Client Compiler
sun.os.patch.level     Service Pack 3
user.country     GB
user.dir     C:\product\11.2.0\dbhome_2\owb\bin
user.home     U:
user.language     en
user.name     bharadwajvenkatraman
user.timezone     Europe/London
user.variant
windows.shell.font.languages
Extensions
Name     Identifier     Version     Status
====     ==========     =======     ======
Check For Updates     oracle.ide.webupdate     11.1.1.0.30.51.07     Loaded
Code Editor     oracle.ide.ceditor     11.1.1.0.30.51.07     Loaded
Component Palette     oracle.ide.palette1     11.1.1.0.30.51.07     Loaded
Help System     oracle.ide.help     11.1.1.0.30.51.07     Loaded
Log Window     oracle.ide.log     11.1.1.0.30.51.07     Loaded
Mac OS X Adapter     oracle.ideimpl.apple     11.1.1.0.30.51.07     Loaded
Navigator     oracle.ide.navigator     11.1.1.0.30.51.07     Loaded
OWB     oracle.owb     11.2     Loaded
Object Gallery     oracle.ide.gallery     11.1.1.0.30.51.07     Loaded
Oracle IDE     oracle.ide     11.1.1.0.30.51.07     Loaded
Peek     oracle.ide.peek     11.1.1.0.30.51.07     Loaded
Property Inspector     oracle.ide.inspector     11.1.1.0.30.51.07     Loaded
Web Browser and Proxy     oracle.ide.webbrowser     11.1.1.0.30.51.07     Loaded
oracle.ide.indexing     oracle.ide.indexing     11.1.1.0.30.51.07     Loaded
palette2     oracle.ide.palette2     11.1.1.0.30.51.07     Loaded
Birdy
Edited by: birdy on 18-Apr-2011 08:56

Process flow - Integrating all modules

Similar Messages

Maybe you are looking for