VPRS issue in STO - IC Billing process flow

Hi Experts,
I am working on following process flow (Stock transport PO - Delivery - Intercompany billing).
Same condition type ZIXX is maintained in MM & SD Pricing procedure. In PO (STO), ZIXX is determined based on material valuation data and the same amount gets copied to IC billing.
Along with ZIXX, we have VPRS condition type in billing pricing procedure. But issue is that: VPRS does not get determine. System analysis shows message 217 (error in quantity/ value determination for VPRS).
Meanwhile, condition amount for ZIXX (determined in PO) and VPRS (determined in IC billing) may differ in some of the business scenarios. So both condition types are needed.
Following settings have been maintained:
·         Copy control settings between delivery & IC billing document
o   Price source A (Purchase order)
o   Pricing type C (Copy manual pricing elements and redetermine others)
·         Item category (Intercompany) has marked for ‘Determine cost’ with billing relevance as A (delivery related billing)
·         Condition type VPRS
o   marked as G (Internal Price)
o   marked for ‘quantity conversion
o   marked as ‘statistical’ in billing pricing PP
o   subtotal B and requirement routine 4 (Cost)
·         Condition type ZIXX
o   Marked as G (Internal price) in MM Pricing procedure
o   Marked as H (Basic Price) in SD PP with requirement routine as 2 (item with pricing)
·         Material type is updated for ‘quantity and value update’ in SAP T.Code: OMS2
Kindly let me know, how we can resolve VPRS issue.

Hi Sachin,
For the similar issue you face, there has been a discussion in the forum.. Pls check
VPRS retrives the cost of the Material from the material master data > Accounting 1 tab to the Sales order.
Once the cost is found, then Profit margin (Net value - cost) is calculated.
VPRS does not contain any Access sequence.
With the help of its Condition category "G", it accesses the Material master > Accounting tab 1 and takes cost.
There may be two cost specified in the Material master. They are
- Moving Avarage Price
- Standard Price
Which one system will consider that depends upon the "Price control" field.
If the value is "V' in the Price control field, the system takes the "Moving Avarage Price" and if it is "S", then system takes the "Standard Price".
So, you must ensure these few control
- VPRS should NOT have any Access sequence.
- Condition category "G" must have been assigned to VPRS.
- VPRS must have been activated as "Statistical" condition in the Pricing Procedure and should not have any Account key.
With Regards
S.Siva

Similar Messages

Issue when generating XPDL from process flows

I have a process flow which has the following architecture.
It begins with a Start activity called “START1”. START1 has two parameters P_MESSAGE_TYPE and P_MESSAGE_ID. These parameters are populated from values provided by an external process. From START1 an unconditional transition goes to a ROUTE activity. Leaving the ROUTE activity are 18 conditional transitions and 1 unconditional transition.
The 18 conditional transitions each perform a test on the parameter value supplied in P_MESSAGE_TYPE. The value supplied is checked against a string value (they all check for different values, e.g. 'referenceEngineeringInstructionRecordExtract'). The 1 unconditional transition provides an “emergency exit” should something come through that does not match any of the 18 conditions.
If there is a match against one of the 18 conditions then that particular transition is followed and a sub-process on the end of that transition is executed. Flow then continues from that sub-process on to an OR operator (which brings together the exit transitions from all 18 of these sub-processes) before the flow ends with the ususal Success, Error and Warning activities.
Here is the problem. When I build this process flow from scratch it generate out the XPDL it works fine. The XPDL generated around some of the conditional transitions looks like this:
<Transition Id="TRANSITION_4" From="MESSAGE_TYPE_ROUTER" To="R_EI_PART_CHANGE">
<Condition Type="CONDITION">
<Xpression>"P_MESSAGE_TYPE" ='referenceEngineeringInstructionPartChangeRecordExtract'</Xpression>
</Condition>
</Transition>
<Transition Id="TRANSITION_5" From="MESSAGE_TYPE_ROUTER" To="R_ENGINEERING_INSTRUCTION">
<Condition Type="CONDITION">
<Xpression>"P_MESSAGE_TYPE" ='referenceEngineeringInstructionRecordExtract'</Xpression>
</Condition>
</Transition>
<Transition Id="TRANSITION_6" From="MESSAGE_TYPE_ROUTER" To="R_FATIGUE">
<Condition Type="CONDITION">
<Xpression>"P_MESSAGE_TYPE" ='referenceFatigueParameterRecordExtract'</Xpression>
</Condition>
</Transition>
Here the complex condition in the transitions can be seen as, for example, *"P_MESSAGE_TYPE" ='referenceEngineeringInstructionPartChangeRecordExtract'* which appears in the process flow editor in the form *"START1"."P_MESSAGE_TYPE"='referenceEngineeringInstructionPartChangeRecordExtract'*
and these are all consistent throughout, i.e. every transition in thn process flow editor shows the “START1” which then seems to get stripped off during the XPDL generation.
Now, if I make a change to the flow (e.g. remove a sub-process or add a new sub-process) and regenerate the XPDL what usually gets generated is of this form:
<Transition Id="TRANSITION_4" From="MESSAGE_TYPE_ROUTER" To="R_EI_PART_CHANGE">
<Condition Type="CONDITION">
<Xpression>"P_MESSAGE_TYPE" ='referenceEngineeringInstructionPartChangeRecordExtract'</Xpression>
</Condition>
</Transition>
<Transition Id="TRANSITION_5" From="MESSAGE_TYPE_ROUTER" To="R_ENGINEERING_INSTRUCTION">
<Condition Type="CONDITION">
<Xpression>"START1"."P_MESSAGE_TYPE" ='referenceEngineeringInstructionRecordExtract'</Xpression>
</Condition>
</Transition>
<Transition Id="TRANSITION_6" From="MESSAGE_TYPE_ROUTER" To="R_FATIGUE">
<Condition Type="CONDITION">
<Xpression>"P_MESSAGE_TYPE" ='referenceFatigueParameterRecordExtract'</Xpression>
</Condition>
</Transition>
What can be seen here is that for some reason the generator has kept the “START1” context of P_MESSAGE_TYPE in the test for referenceEngineeringInstructionRecordExtract (and for two others that I haven't included) but not for the remaining 15 which appear as normal. This results in code that falls over at runtime. I haven't touched these conditional transitions between edits. They are uniquely sequenced and the process flow validates successfully.
Has anyone else seen this issue before? I can’t find any reference to it either in MetaLink or in the forums.
Edited by: AndrewD on Jul 3, 2009 1:57 PM

Hi David,
Thanks for the reply. The client version is 10.2.0.2.8 on a 10.2.0.2 repository. I suspect that it is something internally buggy. I have since found other issues - like I open up one process flow and choose the "Generate" option from the menu, whereupon it generates the XPDL for the last process I opened and not the current one...seems like there are several issues in this area.
Andrew

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

Performance issues executing process flows after upgrading db to 10G

We have installed OWF 2.6.2, and initially our database was at 9.2. Last week we updated our database to 10g, and process flow executions are taking a lot longer, from 1 minute to 15 minutes.
Any ideas anyone what could be the cause of this performance issue?
Thanks,
Yanet

Hi,
Oracle10g database behaves differently on the statistics of tables and indexes. So check these and check wether the mappings are updating these statistics at the right moments with respect to the ETL-proces and with the right interval.
Also, check your generated sources on how statistics are gathered (dmbs_stats.gather....). Does the index that might play a vital role in Oracle9i get new statistics, or only the table? Or only the table where doubled in amount of rows by this mapping?
You can always take matter into your own hands, by letting OWB NOT generate the source for gathering statistics, and call your own procedure in a post-mapping.
Regards,
André

Issue in STO process-"only 0 MT of material available".

Hi All,
I am facing this issue during STO processing using mvt scenario 15 & 16. Let say that i have 5Mt of material stock left at plant A(dispatch plant). When create the load ticket(mvt-15) for the same qty , the ticket is created successfully. Now when i do the unloading ticket(with mvmt 16) the delivery doc gets created with the following error message-"only 0 MT of material available".
I have checked the stock, and the stock is available for at the dispatch plant. Am i missing some configuration settings ?
regards
srinivas

Hi Srinivas,
Have you tried pegging the two line items or even "Auto Pegging"?

I want to know the process flow in Bill Of Service (BOS)

I want to know the process flow in Bill Of Service (BOS)

please refer to link http://scn.sap.com/message/14200963.

Using of user defined activities in process flow: issue

Hi out there,
there is a problem in my environment which I don't understand and which I want to share with you. Hopefully there is somebody who can help me.
I have a user defined activity in my process flow with the following parameters (where <empty> means no value):
COMMAND: C:\WINDOWS\system32\cmd.exe
PARAMETER_LIST: <empty>
RESULT_CODE: <empty>
SCRIPT: C:\oracle\bise1\scripts\source_file.bat
SUCCESS_THRESHOLD: 0
The bat-file is containing the following:
cd c:\oracle\bise1\owb\owb\bin\win32\
ombplus.bat c:\scripts\source_files.tcl
exit
When I execute the bat-file in the cmd-shell manually it works perfect (the tcl-script copies and renames sourcefiles to naming conventions). But when I want to execute this from the process flow nothing happens. The process is running without reading the correct source files and therefore ends in errors.
Is there anything wrong in the usage of the user defined activity? I prepared the runtime properly.
Any help is appreciated. :-)
Kind Regards,
Jens

Hi Detlef,
thanks for the input. I tried it but then I get the following error message (in german) in the logfile of the process flow:
"Der Befehl "chcp" ist entweder falsch geschrieben oder konnte nicht gefunden werden."
My scripts don't contain letters in this combination. The scripts are working fine when I start them manually from the command shell. Is there maybe something else I need to consider? Is it possible to start omb tcl-scripts via this feature?
Kind Regards,
Jens

Intercompany STO with consignment processing

Has anyone faced this situation? I have a client who would like to use consignment processing for VMI orders but as the goods do not get stored at the sales organzation/plant/company code that owns the order - they need to procure the goods from another company code? This is almost a mixture of the Intercompany sales process and VMI processing in ECC... Thoughts?
Example:
Company, plant A / Customer 999999999 / Part A - Stock "0"
Company, plant B / Part A - Stock "1000 pieces"
Preferred Sequence:
1. Create the VMI fill-up order KB for customer 999999999 (delivering plant is B, but the sales order belongs to sales org "A")
2. Create the delivery for the VMI fill-up order from plant b
3. Post goods issue for delivery from plant b
4. Create an IC billing document IV between company code B and A (for the goods that have shipped to the customer's consignment location for company A)
5. In MMBE see that the goods are consigned to customer 999999999 for plant A and NOT plant B. Currently, it is not treating the delivery as an intercompany order (as it is consignment and still owned by the other organization). The stock shows under consignment at plant B.
We are trying to decrease the steps from standard processing which would be the following:
1. Create the VMI fill-up order KB for customer 999999999 (delivering plant is B, but the sales order belongs to sales org "A")
2. Create the delivery for the VMI fill-up order from plant b
3. Create an IC STO from Company B to Company A
4. Create a delivery to move the goods from B to company A.
5. Create and IC billing document
6. Post GR for the goods when they arrive in company A.
7. PGI the delivery for the delivery from step 2 to move the goods into consignment.
8. In MMBE see that the goods are consigned to customer 999999999 for plant A

Hi Manoj,
Please confirm the following for your set-up
I have configured same consignment process for our client.
the process flow like this
--> Fillup order
-->Fillup delivery
-->STO (Purchase order) (through batch job) ***DID YOU RUN MRP AT THE RECEIVING PLANT TO CREATE THE IC STO? WHAT MASTER DATA SET-UP/CONFIG DID YOU PUT INTO PLACE? FOR CONFIG, I AM ASSUMING THE STANDARD IC STO CONFIG IN THE MM/PURCHASING/IC STO SECTION...
--> replanishment delivery (through batch job)
PGI of rep delivery
--Intercompany invoice if intercompany sales.
-->MIGO****SOUNDS LIKE THIS WAS STILL A TWO STEP PROCESS TO MOVE THE GOODS INTO THE RECEIVING PLANT WITH A GR USING MIGO AND THEN THE FOLLOWING STEP YOU MENTION BELOW TO MOVE THE STOCK TO THE CUSTOMER'S CONSIGNMENT LOCATION. IS THAT CORRECT?
--MB1B with movement type 631 (through batch job)****HOW DID YOU CREATE THE BATCH JOB TO POST THE MOVEMENT? THIS IS USUALLY A TRANSACTION RUN MANUALLY (UNLESS YOU HAVE CREATED AN INTERFACE THAT HAS THE INFORMATION TO POST)...

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

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

Mm process flow

hi
will any body give a complete life cycle flow of material management module or product life cycle management of mm module
regards
brijesh

MM Process flow:
The typical procurement cycle for a service or material consists of the following phases:
1. Determination of Requirements
Materials requirements are identified either in the user departments or via materials planning and control. (This can cover both MRP proper and the demand-based approach to inventory control. The regular checking of stock levels of materials defined by master records, use of the order-point method, and forecasting on the basis of past usage are important aspects of the latter.) You can enter purchase requisitions yourself, or they can be generated automatically by the materials planning and control system.
2. Source Determination
The Purchasing component helps you identify potential sources of supply based on past orders and existing longer-term purchase agreements. This speeds the process of creating requests for quotation (RFQs), which can be sent to vendors electronically via SAP EDI, if desired.
3. Vendor Selection and Comparison of Quotations
The system is capable of simulating pricing scenarios, allowing you to compare a number of different quotations. Rejection letters can be sent automatically.
4. Purchase Order Processing
The Purchasing system adopts information from the requisition and the quotation to help you create a purchase order. As with purchase requisitions, you can generate Pos yourself or have the system generate them automatically. Vendor scheduling agreements and contracts (in the SAP System, types of longer-term purchase agreement) are also supported.
5. Purchase Order Follow-Up
The system checks the reminder periods you have specified and - if necessary - automatically prints reminders or expediters at the predefined intervals. It also provides you with an up-to-date status of all purchase requisitions, quotations, and purchase orders.
6. Goods Receiving and Inventory Management
Goods Receiving personnel can confirm the receipt of goods simply by entering the Po number. By specifying permissible tolerances, buyers can limit over- and underdeliveries of ordered goods.
7. Invoice Verification
The system supports the checking and matching of invoices. The accounts payable clerk is notified of quantity and price variances because the system has access to PO and goods receipt data. This speeds the process of auditing and clearing invoices for payment.
Common Tables used by SAP MM:
Below are few important Common Tables used in Materials Management Modules:
EINA Purchasing Info Record- General Data
EINE Purchasing Info Record- Purchasing Organization Data
MAKT Material Descriptions
MARA General Material Data
MARC Plant Data for Material
MARD Storage Location Data for Material
MAST Material to BOM Link
MBEW Material Valuation
MKPF Header- Material Document
MSEG Document Segment- Material
MVER Material Consumption
MVKE Sales Data for materials
RKPF Document Header- Reservation
T023 Mat. groups
T024 Purchasing Groups
T156 Movement Type
T157H Help Texts for Movement Types
MOFF Lists what views have not been created
A501 Plant/Material
EBAN Purchase Requisition
EBKN Purchase Requisition Account Assignment
EKAB Release Documentation
EKBE History per Purchasing Document
EKET Scheduling Agreement Schedule Lines
EKKN Account Assignment in Purchasing Document
EKKO Purchasing Document Header
EKPO Purchasing Document Item
IKPF Header- Physical Inventory Document
ISEG Physical Inventory Document Items
LFA1 Vendor Master (General section)
LFB1 Vendor Master (Company Code)
NRIV Number range intervals
RESB Reservation/dependent requirements
T161T Texts for Purchasing Document Types
Transaction Codes:
RFQ to Vendor - ME41
Raising Quotation - ME47
Comparison of Price - ME49
Creation of PO - ME21N
Goods Receipt - MIGO
Invoice (Bill PAssing) - MIRO
Goods Issue - MB1A
Physical Inventory - MI01( Create doc)
MI04 (Enter Count)
MI07 (Post)
Also please check this links.
http://www.sapgenie.com/sapfunc/mm.htm
http://www.sap-basis-abap.com/sapmm.htm

Recognize COGS in intercompany billing process

Dear expert,
I read the intercompany billing process and have some confuse.
The process like that: CC1(company code 1) sells to end customer, CC2 (conpany code 2) (internal relationship) issues good.
1, CC1 sells to end customer. CC1 create the SO
2, CC2 creates the DO and PGI, that recognize the COGS at CC2 for the internal sales.
3. CC1 creates the billing to end customer --> record the revenue of CC1
4. CC2 creates the internal billing to CC1 --> record the internal revenue of CC2
My question is, follow this process, I don't see the COGS of CC1, there is only a outbound delivery create by CC2 and COGS of CC2.
I read the document about cross transaction, but it guide me only for steps above.
Are there any mistake here?
Please give me a help.
Thank you in advance!
HongDM

Dear expert,
I have some question about the document flow of the intercompany billing process.
Company code 1 (CC1) sell to customer
CC2 issue goods to customer of CC1, then internal billing to CC1.
the step as below:
1. CC1 create SO (sell to customer)
2. CC2 create outbound delivery to Customer of CC1, recognize COGS of CC2
3. CC1 bill to customer, recognize revenue of CC1
4. CC2 create internal invoice to CC1, recognize revenue of CC2
in internal invoice of CC2, update the output RD04. Does it recognize COGS and goods receipt to CC1? Because as above document flow, I see that, the CC1 don't have COGS, not receipt goods to plant of CC1 and Account Payable for CC2. There my thinking as logic of flow, but I'm not sure what the EDI and RD04 can do. Can you tell me about that.
Thank you very much, this is very helpful for me.
Best regard,
HongDM

Describe the process flow in MM

hi i m new to MM,
can u pls describe the process flow in MM
thanks

Hi Sudeep,
The MM flow is as follow:
1) Purchasing Requsition -> sent by inventory dept to purcharsing dept
2) Request for Quotation(RFQ)-> Purchasing Dept shall ask the vendors to give the quotation for the requested materials by inventory.
3) Quotation -> Quotation is sent by vendors to the company
4) Purchase order-> Based on all paramers of a quotation sent by vendors. Vendors are selected from whom the material has to be obtained. The company gives purchase order to the vendor.
5) Good's receipt -> vendors sends the goods to the company with goods receipt
6) Invoice verification -> this done based on good's receipt. this means that the ordered goods have reached or not.
7) Payment -> payment is done based on invoice verification. this is (FI/CO) *-- Santosh Kumaar.M
Full MM Transaction Codes Flow with table
Purchase Requisition ME51N (Table - EBAN)
RFQ to Vendor - ME41 (EKPO, EKKO)
Raising Quotation - ME47 (EKPO, EKKP)
Comparison of Price - ME49 (EKPO, EKKO)
Creation of PO - ME21N (EKPO, EKKO, EKBE, EKPN, EKKN, EKPV)
Goods Receipt - MIGO (MSEG)
Invoice (Bill PAssing) - MIRO (BSEG)
Goods Issue - MIGO (MSEG)
Physical Inventory - MI01( Create doc) (ISEG)
MI04 (Enter Count) (ISEG)
MI07 (Post) (ISEG)
Hope this helps.
Reward if useful
Shawn

Wht is Process Flow for 3rd Party Sales

wht is Process Flow for 3rd Party Sales

Customize the third party sales in summary:
1. Create Vendor XK01
2. Create Material u2013 Material Type as "Trading Goods". Item category group as "BANS".
3. Assign Item Category TAS to Order type that you are going to use.
4. A sale order is created and when saved a PR is generated at the background
5. With reference to SO a PO is created (ME21N). The company raises PO to the vendor.
6. Vendor delivers the goods and raises bill to company. MM receives the invoice MIRO
7. Goods receipt MIGO
8. Goods issue
9. The item cat TAS or Schedule line cat CS is not relevant for delivery which is evident from the config and,   therefore, there is no delivery process attached in the whole process of Third party sales.
10. Billing      *-- Seema Dhar
SD - 3rd party sales order Create Sales Order
VA01
      Order Type
      Sales org, distr chnl, div
      Enter
      Sold to
      PO #
      Material
      Quantity
      Enter
      Save
SD - 3rd party sales order View the PR that is created with a third party sales order
VA01
      Order Number
      Goto Item Overview
      Item ->Schedule Item
SD - 3rd party sales order View the PR that is created
ME52N
      Key in the PR number
      Save
SD - 3rd party sales order Assign the PR to the vendor and create PO
ME57
      Key in the PR number
      Toggle the "Assigned Purchase Requisition"
      Execute
      Check the box next to the material
      Assign Automatically button
      Click on "Assignments" button
      Click on "Process assignment"
      The "Process Assignment Create PO" box , enter
      Drag the PR and drop in the shopping basket
      Save
SD - 3rd party sales order Receive Goods
MIGO_GR
      PO Number
      DN Number
      Batch tab , click on classification
      Serial Numbers tab
      Date of Production
      Flag Item OK
      Check, just in case
      Post
      Save
SD - 3rd party sales order Create Invoice
MIRO
      Invoice Date
      Look for the PO , state the vendor and the Material
      Check the box
      Clilck on "Copy"
      Purchase Order Number (bottom half of the screen)
      Amount
      State the baseline date
      Simulate & Post
      Invoice Number
      *Invoice blocked due to date variance
SD - 3rd party sales order Create a delivery order
VL01N
      In the order screen , go to the menu Sales Document , select "Deliver"
      Go to "picking" tab
      State the qty and save
SD - 3rd party sales order Create a billing document
VF01
      Ensure that the delivery document is correct in the
      Enter
      Go to edit -> Log
      Save

VPRS issue in STO - IC Billing process flow

Similar Messages

Maybe you are looking for