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

Similar Messages

  • Integration Process flow

    outbound
    What info I should give, if I want to receive data from other microsoft systems for them to develop a webservice/ integration object?
    anyone tell me basics of integration flow?

    Let me know the steps how the siebel generates WSDL and things need to be taken care at dotnet side (for authentication) for
    1. Outbound from Siebel
    2. Inbound to Siebel

  • 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 ID’s (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>

  • 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

  • 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

  • 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.

  • Process flow of bpel process deployment in production server

    Hi,
    Can anyone please explain me the process flow of bpel process deployment in prodcution server . I mean the procedure that we follow for deployment in productions server , what are the steps that we follow , approval from any teams? .....
    Thanks,
    Beginner.

    A quick answer is:
    1. make sure you defined the Application/Integration Server in your developer (user/pass you have - if not oc4jadmin then one the IT gave you).
    2. Deploy your project to that server.
    3. Choose the correct domain in the Console when deploying.
    Is this what you wanted to know???

  • Process flow in EWM

    hi all,
    i am a mm consultant presently now in to integration part of SAP ERP with SAP EWM.
    I want to know the basic concepts and the process flow of SAP EWM.
    BASIC STEPS FOR INBOUND AND OUTBOUND CONFIGURATION IN sap EWM.
    Regards,
    velu

    Hi,
    High level:
    EWM is based on deliveries which are replicated from the ECC system. Master data (materials, vendors etc) is replicated via the core interface from APO (CIF).
    You assign a dummy 3-digit WM number to an EWM SLOC. In EWM, you assign the 3 digit WM number to a 4-digit EWM number. Furthermore, the supply chain unit (is masterdata) is important as well and gets assigned to the EWM number.
    You need to map the delivery types and categories to EWM as the deliveries are the main component in EWM. Most of the customizing is based on condition technique which makes it flexible. HU's are important as well. After receiving for example the inbound delivery in EWM, it becomes an inbound delivery notification. Depending on the processing status, it becomes an inbound delivery. After finishin the processing of the delivery, EWM reports back to ECC and the status of the delivery is updated in ECC again.
    There are some new features; labor management, slotting and rearrangement etc which can be usefull.
    Regards,
    MdZ

  • Process flow with configuration for online payment of vendors

    Dear friends,
    I need the process flow with configuration for online payment to vendors through rtgs or neft.
    Please help me in this regard. One of my client wants to implement online payment process instead of cheque payment.
    thanks and regards
    satya

    1) Payments are initiated at the corporate SAP System using APP and converted into IDOC
    Could you please tell me the steps in converting the app into idoc.
    There are standard Idoc used for the same , for APP it would be PAYEXT, You need to use this Idoc type.
    You define the EDI payment method and assign the program in FBZP (RFFOEDI1)which would created payment medium.
    i believe in the app we will create the proposal and run the payment run, after payment proposal created what are the config steps involved in createing the payment run. for example for checque payment we will maintian variant for cheque printing.
    The payment run config is done in FBZP, which would include definf check PM and assigning house bank sub gl etc.
    2) PI at Client End receives the input through IDOC for the payments
    Pl means? and how the client will recieve this idoc what is the set up has to be made?
    PI(Process Integration) middleware which will send bank files from sap to bank and vice versa.
    3) Bank PI receives the payment and converts the same RTGS/NEFT format
    4) Payment Data is received at the Bank RTGS/ NEFT server for further processing
    how the payment data will be recieved by bank what is the process?
    This is again via PI or any thoird party tool which will send bank files to sap as Idoc, The idoc message type is FINSTA.
    or this in SAP you will have to configure the following:
    *House bank with partner profile
    *Outbound parameters                      what is meant by outbound paramenters and how to create and where to maintian
    *Inbound parameters                          what is meant by inbound paramenters and how to create and where to maintian
    The outbound and Inbounmd idoc's are the one which we send(PAYEXT) and rec from bank(FINSTA).  you create partner profile in WE20 and create partner profile once you create you assign outbound and inbound message types in there.
    *EDI Compatible payment methods        how to know about the compaitable payment methods
    Please goto house bank FI12 and you will see this in there, assign the PM used.
    *APP config                                        i know the app config for cheque payment, for this scenairo any additional settings?
    It would be pretty much same, you will have to define the PM used and Payment medium and remaining configuration in FBZP.
    *Bank details in Vendor :
    You will have to maintain the bank details of the vendor in vendor master.

  • How to configure Integration Directory for Integration process async sync

    Hi Experts,
                     I am confused about doing configuration in Integration Directory i.e receiver determination,interface determination and receiver agreement and sender agreement for my integration process as it involve synchronous send at target side.
    In my Scenario , we get Purchase order request(asynchronously) from SRM system in proxy xml format which we have to map to Cxml format send it to third party system(say system 2) as http request.Then we will recieve a response from system2 in Cxml format through HTTP.Now,we have to map this response as to SRM system via proxy code for successful and error case .If error occured we also have to mail to the respective department about the error occured via mail adapter.Proxy to XI is a asynchronous communication and XI to System2 is a synchronous communication .Then again XI to SRM is a asynchronous communication via proxy.I have request and response External defination for Cxml i.e HTTP side.
    I have done following integration process in ESR
    Start- Receive(1)---Transformation(2)-send(3)-Fork(4)--
    stop
    ...................................................................................................... .....[----Branch 1 [-Transformation(5)-Send(6)-
    .......................[-----Branch 2 -
    SWITCH STEP to check error code[
    ............................................................................................................[.otherwise branch of switch
    Fork(4)----[
    .......................[----Branch 1-Transformation (9)-send(10)-
    Here,
    Recieve(1) -- is used for recieve request from SRM.Mode is asynchronous
    Transforamtion(2)-- is used for operation mapping between request of SRM to HTTP request.
    send(3) --is used to sending request synchronous to HTTP,mode is synchronous,used synchronous abstract interface,abstract reqhttp and abstract resphttp
    switch-switch Branch1 is used for checking error response to be true---
    Transformation(5)--- is used to map HTTP response to Mail response structure
    Send(6)----
    is used to send mail content to Mail adapter
    Transformation(9)---- is used to map HTTP response to Proxy response
    Send(10) --- used to send mapped proxy response to SRM as to update status by calling calling Function module using proxy code.
    Thanks
    Deepak

    Deepak,
    In BPM data does not flow in Backword direction!
    take any step in your BPM the message it is goiong to receive will be what a step just before it is giving to BPM.
    Now in your case
    IR Part:
    You have to call Third part Synchronously and the input to it will be what Proxy has given to you.
    Create an Abstract Synchronous(in case of abstract you need not bother it is Inbound or Outbound) in which(I mean the Message Interface) The Output message will be what you have Received from Proxy and the input message will be what you are going to receive from the Third party as a Response.  Now you would have Inbound Synchronous Interface created for calling Third party.
    Have a Interface Mapping between the Abstract Synchronous and Inbound Synchronous Message Interface.
    ID Part:
    For synchronous Step:  BPM will; be sender with  Message Interface Abstarct Synchronous
    Third Party will be receiver With Inbound Interface(Synchronous). Use the INterface Mapping between Abstract Synchronous and Inbound Synchronous that You have created in IR.
    Have a Receiver Agreement for the Thirs part.
    No Sender agreement required in case of BPM as a Sender.
    Thanks,
    Sunil Singh

  • Integration Process in BPM's

    Hi 
      I'm new to BPM's ... my scenario is I'm doing Multiple files to Single file scenario.. i have two sender files.. and  one receiver file... for this i need to use BPM for merging the message.. 
    I created  all the objects as specified by the blogs..(Message Interfaces ,Message mappings )
    but in integration process i stucked... can any one give me the  steps.. whta i need to do .. I mena.. what are the options can i select...
    <b>Start -> Receiver- Sender1 -
    Sender2 -
    Stop</b>
    like this.. can you plz give me the  flow.. based on that i will  create...
    thanks
    babu

    Hi,
    Check below links for BPM concept.
    /people/krishna.moorthyp/blog/2005/06/09/walkthrough-with-bpm
    /people/shabarish.vijayakumar/blog/2005/08/03/xpath-to-show-the-path-multiple-receivers
    /people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit
    /people/sravya.talanki2/blog/2005/08/24/do-you-like-to-understand-147correlation148-in-xi
    /people/michal.krawczyk2/blog/2005/09/04/xi-do-you-realy-enjoy-clicking-and-waiting-while-tracing-bpm-steps
    /people/sudharshan.aravamudan/blog/2005/12/01/illustration-of-multi-mapping-and-message-split-using-bpm-in-sap-exchange-infrastructure
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/media/uuid/daea5871-0701-0010-12aa-c3a0c6d54e02
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/media/uuid/e8515171-0701-0010-be98-e37bec4706cc
    Regards,
    Phani
    Reward points if Helpful

  • Process flow/map performance issues

    We have some issues with our OWB-based application and we're looking to find out if there are different ways we could be using the tool, or features/options we've missed.
    We are trying to maintain a near real time feed of data from a front end system into our warehouse which was built using OWB 10.2.0.3 over a 10.2.0.4 database. The bulk of the application consists of OWB maps with a few hand-written PL/SQL objects, all executed in a series of hierachical OWB process flows. Maps/transformations are executed either sequentially or in parallel where the referential integrity of the model allows.
    The problem is that we have around 150 tables in the datamart which could potentially require updating on each refresh cycle, although in practice only a few tables have any activity on a typical refresh cycle. The cycle consists of loading data into a set of staging tables, and from there the data is transformed into the main schema, often with multiple maps per target table.
    On every cycle we run hundreds of maps, the vast majority of which process zero rows. Each map runs quickly and efficiently in its own right but collectively they add up to a 5 - 10 min cycle even if there is no data to process.
    There are 2 avenues which we'd like to explore and would be grateful if anyone could provide any pointers/suggestions :-
    1) It appears that each map opens and closes its own database session when it executes. I presume this was done because a single process flow could be constructed with maps executing in different target schemas, but we know that's not the case for us. We'd like to know if there is anyway to configure the database connection at a higher level (eg. process flow) so it opens a connection once and executes each of the maps (database packages) in that one session.
    Our DBAs are experimenting with 'shared server' settings at a database level which may help to some degree but won't be the whole story.
    2) Another option is simply to run less maps eg. load the staging area as now, collate stats on which staging tables contain new data, and then apply some logic such that subsequent maps only execute if the relevant staging table(s) contain(s) some new data, otherwise bypass that map.
    We tried experimenting with the 'Pre Mapping Process' operator, but essentially that just generates another function call from the map package, so we still have the overhead of opening a database session for each map to run the package. Minimal gain.
    We thought about adding a function call in the process flow before each map and then branching to either execute/bypass the map as approriate, but the function call still requires opening/closing of a database session each time so, once again, minimal gain.
    What we really want is some way for a map or process flow to check without logging onto the database repeatedly.
    Any ideas on the above, or other potential solutions anyone could suggest, would be greatly appreciated.

    Hi,
    Please see if these documents help.
    Note: 554635.1 - Create Accounting Process Performs Poorly When 100K + Distributions are Passed for an Event
    Note: 954273.1 - Multiple Create Accounting Requests Result In Poor Performance For Online Accruals
    Note: 763500.1 - R12: Performance Issue with Create Accounting
    Note: 733637.1 - R12:Performance Issue When Running Accounting Program Xlaaccup
    Note: 781311.1 - Create Accounting Process Taking A Long Time To Complete After Appying Critical Patches
    Note: 557869.1 - EBS: R12 Oracle Financials Critical Patches
    Regards,
    Hussein

  • 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 data’s 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
    &#61692;     Master Data
    &#61692;     Sales Support
    &#61692;     Sales
    &#61692;     Shipping
    &#61692;     Billing
    &#61692;     Credit Management
    &#61692;     Foreign Trade / Customs
    &#61692;     Sales Information System
    Master Data
    &#61607;     Business Partner / Customer
    &#61607;     Products
    &#61607;     Conditions
    &#61607;     Agreements / Contracts
    &#61607;     Terms of Payment
    &#61607;     Incoterms
    &#61607;     Routes
    Sales Support
    &#61607;     Sales Promotions
    &#61607;     Sales Activities
    &#61607;     Potential Analysis
    Sales
    &#61607;     Inquiry
    &#61607;     Quotation
    &#61607;     Order / Contract / Backorder
    &#61607;     Product Proposals
    Shipping and Transportation
    &#61607;     Outbound Delivery
    &#61607;     Picking
    &#61607;     Packing
    &#61607;     Loading
    &#61607;     Shipment
    &#61607;     Post Goods Issue
    &#61607;     Billing
    Billing
    &#61607;     Billing
    Credit Management
    Foreign Trade / Customs
    Sales Information System
    Activities Involved by the SAP – SD End User
    &#61656;     Inquiry Processing  
    &#61656;     Quotation Processing  
    &#61656;     Contract Processing 
    &#61656;     Sales Order Processing   
    &#61656;     Scheduling Agreement Processing
    &#61656;     Returns Processing 
    &#61656;     Rebate Processing  
    &#61656;     Sales Deal and Promotion Processing
    &#61656;     Display Customer and Material Information
    &#61656;     Billing Processing (online)
    &#61656;     Billing Processing (In The Background)
    &#61656;     Invoice List Processing
    &#61656;     Maintain Customer and Material Information
    &#61656;     Display Pricing
    &#61656;     Maintain Pricing 
    &#61656;     Release Blocked Documents for Billing
    &#61656;     Release Sales Orders for Delivery
    &#61656;     Display Sales Information
    &#61656;     Display Billing Documents
    &#61656;     Sales Analysis
    &#61656;     Credit Management in Sales and Distribution Documents
    &#61656;     Backorder Processing   
    &#61656;     Sales Support
    &#61656;     Output Processing 
    Inquiry Processing
    &#61607;     Create/change/display inquiries
    &#61607;     Generate lists for inquiries and incomplete inquiries
    &#61607;     Select sales documents according to object status
    Quotation Processing
    &#61607;     Create/change/display quotations
    &#61607;     Generate lists for quotations and incomplete quotations
    &#61607;     Select sales documents according to object status
    Contract Processing
    &#61607;     Create/change/display contracts
    &#61607;     Generate and process list of contracts
    &#61607;     Generate and process list of incomplete contracts
    &#61607;     Select sales documents according to object status
    Sales Order Processing
    &#61607;     Create/change/display sales orders
    &#61607;     Generate and process list of sales orders
    &#61607;     Generate and process list of incomplete sales orders
    &#61607;     Select and process sales documents according to object status
    &#61607;     Select and process sales documents in a period of time
    &#61607;     Select and process duplicate sales documents in a period of time
    Scheduling Agreement Processing
    &#61607;     Scheduling agreement processing
    &#61607;     Select and process incomplete scheduling agreements
    &#61607;     Select sales documents according to object status
    Returns Processing
    &#61607;     Create/change/display sales orders
    &#61607;     Create/change outbound delivery
    Rebate Processing
    Rebate processing:
    &#61607;     Maintain rebate agreements
    &#61607;     Extend rebate agreement
    &#61607;     Settlement of rebate agreements
    &#61607;     Generate list of rebate agreements
    Billing document:
    &#61607;     Display billing document
    &#61607;     Compare the rebate basis from billing documents and statistics
    &#61607;     Update billing documents referring to rebate conditions
    Sales Deal and Promotion Processing
    &#61607;     Create/change/display sales deals
    &#61607;     Generate list of sales deals
    &#61607;     Create/change/display promotions
    &#61607;     Generate list of promotions
    Display Customer and Material Information
    &#61607;     Display customer (Sales)
    &#61607;     Display material
    &#61607;     Display material listing/exclusion
    &#61607;     Select customer material info record according to customer
    &#61607;     Select customer material info record according to material
    &#61607;     Display customer hierarchy
    &#61607;     Display sales deals
    &#61607;     Display promotions
    &#61607;     Display rebate agreements
    &#61607;     Display cross selling materials
    &#61607;     Display assortment module for value contracts
    Billing Processing (online)
    &#61607;     Create/change/display billing document
    &#61607;     Cancel billing document
    &#61607;     Retroactive billing
    &#61607;     Process billing due list
    &#61607;     Set billing date
    &#61607;     Display billing documents from the archive
    &#61607;     List of billing documents
    &#61607;     Rebook accounting indicator
    &#61607;     Release sales orders for billing
    &#61607;     Display sales and distribution documents blocked for billing
    Billing Processing (In the Background)
    &#61607;     Display billing document
    &#61607;     Generate batch jobs for billing
    &#61607;     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
    &#61607;     Create/change/display invoice lists
    &#61607;     Process work list for invoice lists
    &#61607;     Generate invoice list
    &#61607;     Generate cancellation invoice list
    &#61607;     Display invoice list from the archive
    Maintain Customer and Material Information
    &#61607;     Maintain material listing/exclusion
    &#61607;     Reference material listing/exclusion
    &#61607;     Maintain material substitution
    &#61607;     Reference material substitution
    &#61607;     Maintain material information
    &#61607;     Select customer material information according to material or customer
    &#61607;     Maintain material
    &#61607;     Maintain customer (Sales)
    &#61607;     Maintain customer hierarchy
    &#61607;     Maintain materials for cross selling
    &#61607;     Maintain value contracts
    &#61607;     Maintain Incoterms
    Display Pricing
    &#61607;     Display condition records
    &#61607;     Display condition lists
    &#61607;     Display conditions using index
    &#61607;     Display free goods determination
    Maintain Pricing
    &#61607;     Create/change/display condition
    &#61607;     Condition processing using index
    &#61607;     Create/change/display free good
    &#61607;     Create/change/display condition lists
    &#61607;     Process net price list
    &#61607;     Release expected customer price
    Release Blocked Documents for Billing
    &#61607;     Release sales orders for billing
    &#61607;     Change billing document
    &#61607;     List of blocked billing documents
    Release Sales Orders for Delivery
    &#61607;     Change sales order
    &#61607;     Block and unblock customer from sales view
    &#61607;     Generate lists for incomplete sales documents and for sales documents blocked for delivery
    Display Sales Information
    &#61607;     Generate list for quotations, contracts, sales orders or scheduling agreements
    &#61607;     Generate list for incomplete quotations, contracts, sales orders or scheduling agreements
    &#61607;     Generate list of sales orders blocked for delivery
    &#61607;     Display sales activities, item proposals, material listing and material exclusion
    &#61607;     Sales support monitor
    Display Billing Documents
    &#61607;     Display billing document
    &#61607;     Display list of billing documents
    &#61607;     Display blocked billing documents
    Sales Analysis
    &#61607;     Contracts: Lists for overdue and completed contracts
    &#61607;     Quotations: Lists for overdue and completed quotations
    &#61607;     Backorder processing: Backlog list, selection list
    &#61607;     Generate list for: Inquiries, rebate agreements, scheduling agreements
    &#61607;     Information on the customer: Sales summary, list of top customer
    &#61607;     Material information: List of top materials
    &#61607;     Sales support monitor
    &#61607;     Flexible planning: Display/create/change
    Credit Management in Sales and Distribution Documents
    &#61607;     Process credit authorization for sales and distribution documents
    &#61607;     List of released sales and distribution documents
    &#61607;     List of blocked sales and distribution documents
    &#61607;     Process credit authorization according to sales and distribution document
    &#61607;     Process credit authorization according to delivery
    &#61607;     List of incomplete sales and distribution documents
    &#61607;     Sales and distribution documents blocked for delivery
    &#61607;     Delivery monitor
    &#61607;     List of billing documents
    Backorder Processing
    &#61607;     Display backlogged sales orders
    &#61607;     Process backorder processing using selection list according to sales documents
    &#61607;     Backorder processing: access using the material
    &#61607;     Execute rescheduling of sales documents
    &#61607;     Evaluate rescheduling of sales documents
    Sales Support
    &#61607;     Create/change/display sales activities
    &#61607;     Executing mailing promotions
    &#61607;     Display and create interested parties and contact persons
    &#61607;     Display sales summary
    &#61607;     Sales support monitor
    &#61607;     Display competitive products
    Output Processing
    &#61607;     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

  • FI- process flow charts

    hello,
    .I need FI- process flow charts. like exp: ar,ap,bank.assetaccounting.  like pls help anyone.
    rajesh

    i think u r in blueprint preparation,...
    this list may usefull to u ....
    if you need any details please communicate me...
    1     General Ledger Accounting
    1.1     Vendor/Customer/GL rectification entries, Provisions or Finalization & other JVu2019s
    1.2     Cash Transactions
         Cash Payments
         Cash Receipts
         Entering Contra Entries
         Inter Company Transactions
    1.3     Travelling Expenses
    1.4     Posting Salaries and Wages
    1.5     Process Employee Expenses
    1.6     Posting a Recurring entry
    1.7     Financial Statements u2013 Reports
    2     Accounts Payable Accounting:
    2.1     Automatic Payment Program
    2.2     Partial & Residual Payment Clearing
    2.3     Credit memo u2013 with Reference
    2.4     Manual Invoices & Credit Memou2019s u2013 without Reference
    2.5     Accounts Payable u2013 month end processes
    2.6     Reporting and Transaction details u2013 Over view
    3     Accounts Receivable Accounting:
    3.1     Incoming Payment Processing u2013 bill of exchange
    3.2     Incoming Payment Processing u2013 Returned Payments
    3.3     Dunning process (Reminder Notice)
    3.4     Dunning u2013 BOE
    3.5     Credit notes issued to customers
    3.6     Debit note issued to customers
    3.7     Customer open item clearance
    3.8     Customer reconciliation and Balance confirmation
    4     Asset Accounting
    4.1     Asset Accounting u2013 Over view
    4.2     Fixed Asset Acquisition
    i.     Non-integrated Asset Acquisition Posting u2013 Before Invoice Receipt
    ii.     Non-integrated Asset Acquisition Posting u2013 After Invoice Receipt, with Clearing
    iii.     Subsequent Asset Acquisition
    iv.     Post Capitalization u2013 Write-up to APC
    v.     Acquisition of Fixed asset resulting from extraordinary Revenue
    4.3     Asset under Construction (AUC)
    4.4     Retirement of Assets
    i.     Retirement with Revenue 
    ii.     Posting Gain or Loss on sale of asset
    iii.     Retirement without Revenue (due to Scrapping)
    iv.     Intracompany asset Transfer
    4.5     Periodic Postings
    i.     Recalculating Values
    ii.     Information system - Reporting 
    5     Bank Accounting
    5.1     Bank Receipts u2013 Cheque Deposits
    5.2     Bank Payments u2013 Out going Payments u2013 Over view
    5.3     The Cheque Return Process
    5.4     Cheque Reversal & Realization Process at Head Office
    5.5     BRS u2013 Over view
    5.6     BRS u2013 Incoming Payment Reconciliation
    5.7     BRS u2013 Out going Payment Reconciliation u2013 BRS
    5.8     Impress Accounting System u2013 Process
    5.9     LC management
    5.10     BG Management
    5.11     Cash Flow management u2013 Over view
    6     A Look on Period u2013 End Closing Operations
    6.1     Day u2013 End Closing Operations
    6.2     Month u2013 End Closing Operations (General)
    6.3     Month u2013 End Closing Operations
    6.4     Year u2013 End closing Operations
    Assign ponts if u feel so...

Maybe you are looking for