Purchase order total value

Hi all!
Is there any table or any function module which gives the total value of the purchase order inclusive of all the taxes and conditions?

Hi Gud Afnoon,
Now Try EKBE / EKPO table in SE16 Tc.
U hav to mention PO no there.
Can i hav ur mail Id.

Similar Messages

Purchase Order Total Amount at Header level and Report Execution

Dear Experts,
Here by i am facing problem with Purchase Order Total amount.
I have local Pricing Procedure for price stipulations (like discounts, Freight, packaging). the calculation at item level is correct. tax calculation is done by tax code. The total PO Price is including all items in PO and tax amount. But at header level conditions net value is showing only gross price.
How to pick up total price including tax amount at header level conditions?
Please provide me solution on it ?

Dear Experts,
Here by i am facing problem with Purchase Order Total amount.
I have local Pricing Procedure for price stipulations (like discounts, Freight, packaging). the calculation at item level is correct. tax calculation is done by tax code. The total PO Price is including all items in PO and tax amount. But at header level conditions net value is showing only gross price.
How to pick up total price including tax amount at header level conditions?
Please provide me solution on it ?
Edited by: Kiran Mujumdar on Feb 23, 2009 7:08 PM

Transaction code for sales order totals and purchase order totals

Hi i am using alv grid report to display the sales order and purchase order totals by productline(profit center)
Now i have to call standard transactions from first list to display the totals of sales order and purchase order.I have to display these transctions for specfic orders and their specfic lineitems only.
in VA05n transaction it is allowing me to enter only the document numer but not item.
Can any one help to find the standard transaction to display the totals for only specific orders and line specific line items

Hi Polite,
The transaction CRMD_ORDER is the superset for all the transactions mentioned by you. So it is better to remember just one transaction instead of remembring the subsets . Once you use the transaction CRMD_ORDER and then Follow the menu Business transaction -> Create (F5) you will get the list of transactions you can create this is nothing but the the transactions you have mentioned.
If you know the transaction no. you can directly open that in transaction CRMD_ORDER. The other opetion is to use the SAP Menu instead of transactions.
<b>Reward points if it helps!!</b>
Best regards,
Vikash.

How to Retrieve Purchase order TAX value price

Hi,
I want to retrieve Purchase order TAX value price from the purchase order is there any function module to retrieve this value. Or from which table we can retrieve this value using purchase order no.
Thanks in advance

Hi Pradeep,
Have you looked BAPI <b>BAPI_PRICES_CONDITIONS</b>?
Hope this will help.
Regards,
Ferry Lianto

Restrict Purchase Order Minimum Value

Hi,
We want that the SAP System should not allow the user to create a Purchase Order of Value less than Rs. 5000.
Is there any SAP Standard Functionality available for the same or we need to use the User Exit?
Regards,
PK

Thanks Shital for the reply.
We are not using Release Strategy, hence we want to out the check at the PO Creation level only.
Pls. advise.
Regards,
PK

Purchase Order Condition Value

Hi,
We have an issue with the Conditions in a Purchase Order raised by the client.
In this purchase order, there are 151 items with PB00 or PBXX item conditions.
However when these are totaled up (as a standard SAP functionality) and the values are displayed are at header level, we find that the totaled values are incorrect.
For some values the quantity used for totaling at header level are incorrect.
For eg. For one material, there are 2 line items of 16 qty each which total up to 32 items at 29.25 USD. However the header level shows the amount as 965.25 with amount as 29.25 and qty as 33.
There are many such discrepancies between the header calculations and the item level quantities. In some cases items with PBXX conditions have been totaled up under PB00.
Both PB00 and PBXX are configured as item level conditions only.
This results in Net Value of Purchase Order being wrongly calculated.
Could anybody throw any light on why this happens and how it can be resolved.
Regards
Anjan

Hello Anjan
If u check the condition type PBXX and PB00, in PB00 in Group condition field , 'Group condition' check box needs to 'Tick'. Please check relevant help. I hope due to non tick in condition type, caculation in PO for above condition types are going wrong. Also check with Item and Header tick in condition type.
Regards
Amol

Release Strategies in Purchase Order - possible values of caracteristics

Hello,
I have the following situation at hand.
We use in a company code a release strategy for POs. One of the caracteristics is the "plant" (CEKKO-WERKS, multiple values). Strategy is working fine.
Now I have to implement in another company code- in the same Client - the PO release strategy but this company code has about 800 Plants asociated! moreover, the release strategies in this new company are not dependent on the "plant"!
I can not change the caracteristics in the Release strateg because this would affect the already working strategies and SAP does not allow to asign another Class to the PO release groups.
Is there any way I can prevent that I have to create release strategies with each of them 800 Plants in the caracteristics "Plant" ?
Can I use something generic in the caracteristics field of the strategy?
Thanks for any help. It would save me a lot of time!
Aart

Note 493900 - FAQ: Release Strategy
1. Question :
Why is the release strategy not determined?
Answer :
Please check the following points :
You can not use Release without classification and Release with classification.
If there is an entry present in Release Group table (T16FG-FRGOT) only release with classification can be used.
If you use version management, the determination of the release strategy starts when the version is completed.
You complete a version by setting the "version completed" indicator in the version tab.
Cost Center values (CEBAN-KOSTL) and Vendor values (CEBAN-LIFNR) in the release strategy characteristics should be entered with leading zeros.
This is true for the other structures as well (CEKKO and CESSR). See note 52225.
For OVERALL RELEASE (purchase order and purchase requisition) the item fields such as Plant and Material Group will be aggregated to header level.
For example you use Plant as one of your characteristics. If all items do not belong to the same plant then the relase strategy will not be found unless you have maintained a blank value as one of your allowed values for the characteristic Plant. If all items belong to the same plant then that plant is aggregated to the header; if one or more is different then a blank is aggregated to the header. See note 47089.

Purchase Order item value breakup condition type wise

Dear Sir,
We are developing a custom report and in this report we need to reflect for Purchase Order item wise the break-up of values at the condition type level .
In Me23n , at at Item Level , when we click on tab <Condition> then all values break-up at condition type level gets displayed .
But to use in custom program , we need to know the table where this information is available .
Kindly guide us pl .
Regards
B Mittal

Hi,
This suggestion is based on my understanding of your issue. May not be straight forward SAP solution.
I would suggest you to make following assessment for your custom program: (going through the condition tab will lead you to structures)
1. Try to figure out how the pricing condition are maintained. Normally you have your Base price PBXX or gross price per EA defined that can be found in the PIR of the material + Vendor combination or in the pricing condition you would have defined.
2. In same way figure out all the other absolute condition types. I mean any thing that is not % percentage based on PBXX value. (assess ;your pricing Schema to understand this.
3. Once you know how is your pricing schema breakup then try to pick the net price of PO and then do a backward calcuation based on PIR condition value. .
Hope this helps.
thx
MJ

Purchase Order total weight

Hi Gurus,
I am working on an enhancement to handle the total weight of the purchase order during creation.We need to validate with few custom fields in MARA table to handle small pack and large pack materials based on container group(ZCONGR) . Based on the materials quantity we need to calculate the total weight of the order and if it exceeds 50 tonnes then we need to trigger a warning message to the user who is trying to create.
Please suggest me how can we handle this are there any enhancement where we can handle this requirement. Thanks.
Regards,
Sanjay

Suggestion:
Implement BADI ME_PROCESS_PO_CUST, put you logic in method PROCESS_HEADER.

Purchase order total amount

hi ,
i have 5 line items and each line item has its own individual total according to its quantity . now where will i see the total amount of all the line items in the purchase order
thanks
muthuraman.d

Hi,
In the PO -> HEADER-> CONDITIONS---> Net price
You can find in the CONDITIONS Tab in the field NET PRICE for all the line items ( this is the total amount of PO)
please check that.
regards,
santosh

Purchase Order Discount Value

Gurus,
Need help in getting the source table of discount condition value in purchase order.
This is under the header condition tab. T-code: ME23N
Thanks in advance

Dear Golddust,
1st go to EKKO table, enter PO number, then get the EKKO-KNUMV value, then go to table konv, and paste the KNUMV value in doc.condition, then execute, from there you can get all PO header condition.
Regards,
w1n

Purchase Order Condition values

Hi Friends ,
             I'm facing a problem in identifying a data source for Purchase Order's. On searching in SDN Forum i came to know that there is no standard Datasource for Purchase order conditions.
             Can some one give me little clue of how to pick up the conditions from R/3 to my biw system.
Thanks and Regards,
Vijay

Hi Anil ,
         Thanks for your response.
         On analysing the condition table KONV in R/3 one thing striked my mind.
         Either it's Purchase order or Sale Order the condtion table is one , that is KONV. So if the condition number is available for a PO i think very well we can pick it for po's.
         Can you give me your suggestion on the above...please.
regards,
Vijay

Purchase order Net value

Dear All
We are using SAP 4.7 with Tajinj
In purchases the PO net value not stored in any where in the standard table SAP suggest to maintain the condition type JEXS and i have attached with the respective pricing procedure but the Excise and tax values not capturing in to the pricing procedure.
Any idea?....
Regards
Anand

Hi,
If you using TAXINJ then you first need the Tax codes.
Check whether tax codes are entered in PO then the system will capture the percentage maintained in the Tax code for the PO net order value.
PO net value will be stored in Purchase info record if you have maintain or auto info update is ticked in PO.
When the new PO is creating then system will take this PO net value from Info record & once the tax code is entered in Invoice tab of PO the system will calculate the Excise values according to tax code formula.
check & confirm
rgds
gsc

Query about calculating Purchase Order Total

Sorry, please ignore this. I've realised my stupid mistake now. Sorry for wasting your valuable time.
Edited by: jimr on May 27, 2009 11:07 AM

you have two different REQ numbers,...
.. ah, you found a mistake.. Good,.. please mark this thread as answered

Release Procedure in Indent/Purchase Order

I want to customise release strategy in indent and Purchase order in SAP. Kindly provide me steps to configure this. will apperitiate your efforts.
Manjit

Hi Manjit,
Release Procedure for Purchase Orders
In this section, you set up a release procedure for purchase orders (POs).
Requirements
If you want to use workflow to release POs, you must make the standard and basic settings for workflow (Basis -> Business Management -> SAP Business Workflow).
How do you set üp a release procedure for POs?
To set up the release procedure, you must make a series of settings in Customizing. This section provides you with an overview of the necessary activities.
You must perform the following steps:
1. Create characteristics and classes
For more on this topic, see Edit Characteristics and Edit Classes.
Note
If you wish to link your release procedure to workflow, you must perform steps 2 and 3 . You make these settings in Customizing for Business Workflow (Basis -> Business Management).
Otherwise, continue with step 4.
Define organizational plan
For more on this topic, see Edit Organizational Plan.
Assign standard tasks and activate event-receiver linkage.
For more on this topic, see Perform Task- Specific Customizing.
1. Set up release procedure for RFQs
a) Create release group
b) Create release code
c) Create release indicator
d) Create release strategy
Note
You need only carry out the following step if you wish to link your release procedure to workflow.
e) Assign release code to a user
For more on this topic, see Define Release Procedure for POs.
2. Check release strategies
For more on this topic, see Check Release Strategies.
Further notes
For more information, refer to
· Implementation of a Release Procedure for Purchasing Documents
· Release of Purchasing Documents (SAP Library -> Basis -> Business Management (BC-BMT) -> SAP Business Workflow (BC-BMT-WFM) -> Reference documentation -> BC Workflow Scenarios in the Applications -> MM Materials Management: Workflow Scenarios)
Edit Characteristic (CT04)
In this step, you create characteristics for a release procedure for purchase orders (POs).
Classification characteristics are the criteria for a release condition. If the criteria of a release condition are satisfied, the associated release strategy is assigned to the purchasing document (e.g. purchase order or RFQ).
Example
Release condition for release strategy EA:
Characteristic Characteristic value
Total net value of PO Above $10,000
If the total value of a purchase order exceeds $10,000, release strategy EA is assigned to this PO.
Requirements
In communication structure CEKKO you will find all the fields that can be used as characteristics for a release condition (e.g. BSART for the order type and GNETW for the total order value).
Check which fields you wish to use as characteristics for your release strategy. To do so, choose Tools -> ABAP Workbench -> Development -> Dictionary, enter CEKKO in the field Database table , and choose "Display".
Note
If you wish to define a separate release strategy for the various document categories (PO, RFQ, etc.), you must create a characteristic for each relevant document category.
Activities
1. Create a characteristic for each field from communication structure CEKKO that is to be a criterion for your release strategy. You have a free choice of names for the characteristic.
2. Enter the table name and the field name on the tab page Additional data (for example, table CEKKO for field GNETW).
Note
o Do not select any of the indicators in the area Procedure for value assignment on the tab page Additional data. Only if none of these indicators is marked can you assign a value or value interval to the characteristic when defining your release strategy.
o When you create a characteristic for a currency-dependent field (e.g. GNETW), a box appears in which you must enter the currency for the relevant value. The system then converts the currency of the purchasing document into this currency.
3. Check the data for the chosen field on the tab page Basic data.
If you want to enter several values or a value interval for a characteristic, set the Multiple values indicator in the area Value assignment.
Note
Value intervals can only be specified for numerical values (e.g. an interval of $10,000 to $15,000 for the value of the purchase order.
4. Check the texts for the field on the tab page Descriptions.
5. You can maintain default values for a characteristic on the tab page Values.
If you maintain values here, these values will be displayed as input help under Create Procedure with Classification -> Release Strategy -> Classification . If you wish to use not only the input help but also other values, you must select the Additional values indicator.
Note
You can also maintain ' ' as a default value. For example, for account assignment: ' ' for stock material, 'k' for cost center, and 'a' for asset.
6. If you want to restrict the use of a characteristic to particular class types, specify the relevant class types on the tab page Restrictions. For example, class type 032 for the release strategy.
Further notes
Further information on characteristics is available in this Customizing activity via Help -> Application help.
Customer exits
Customer exit M06E0004 enables you to change the communication structure for determining the release strategy for purchasing documents.
Edit Class( CL02 )
In this step, you create classes for a release procedure for purchase orders (POs).
You use a class to group together characteristics that are to constitute a release condition for a release strategy. In the step "Define Release Procedure for Purchase Orders " you assign this class to the release strategy.
Activities
1. Create a class with the class type 032. You have a free choice of names for the new class (e.g. REL_RFQ for the release of RFQs).
2. Assign a name for the new class on the tab page Basic data.
3. You can view an error message if different characteristics with identical values have been assigned to a class. To be able to do so, select the Check with error message indicator in the Same classification area.
4. If appropriate, select terms to be used as search criteria in searches for your class on the Keywords tab page.
5. Assign your characteristics to the class via the tab page Characteristics.
Further notes
Further information on classes is available in this Customizing activity under Help -> Application help.
Define Release Procedure for Purchase Orders
In this step, you set up the release procedure for purchase orders (POs) and can link it to workflow. (Note that in this context "releasing" means "approving", or giving the "green light" to a document.)
Requirements
· In the case of a release procedure linked to workflow, you must have previously created the user names, positions, jobs, etc. that you here assign to the release code in the organizational plan and must have linked them to the relevant standard tasks in task-specific Customizing (Basis -> Business Management -> Business Workflow -> Perform Task-Specific Customizing).
· You must assign the authorization M_EINK_FRG to the persons who are to be involved in the release procedure ( Authorization Management -> Create Authorization Profiles and Assign to Users).Activities
Here you define the following:
·     Release group
·     Release codes
·     Release indicator
·     Release strategy
·     Workflow
Release group
Create a release group for your release procedure and assign it to a class. In the process, you assign release conditions to the release procedure.
Release codes
Here you create the release codes you need for your release strategy and assign the codes to your release group. If a release code is to be used in workflow, indicate this accordingly in the Workflow field
The Workflow indicator is also used to control role resolution:
·     "1 - Role Resolution with Group, Code and Plant (T16FW)"
Here you use a role resolution that is supplied in the standard system. To do so, you must assign the release point in the section Workflow (see below).
·     "9 - Role Resolution via User Exit"
Here you use the customer exit M06E0005 to define a role resolution of your own.
Release indicators
A release indicator shows the release status of a PO.
Via the following settings, you can define the release indicators you need for your release procedure:
·     The Released indicator is used to specify whether messages (PO documents in output format) may be transmitted for a purchase order with this indicator.
·     The Changeability indicator shows the effect of changes to the PO (a change to a PO may require a new release strategy to be determined, for instance).
·     By means of the Value change indicator, you can specify that the release strategy is to be re-started if a PO is changed and the value of a PO item thereby increases by a certain percentage (e.g. 10%). Set the Changeability indicator to "4 - Changeable, new release in case of new strategy or value change" or "6 - Changeable, new release in case of new strategy or value change/outputted" and enter a percentage in the Value change field.
Attention:
The following release indicators are necessary for every release procedure:
o     Release indicator for initial status
If the PO is subject to a release strategy, it must normally be released before it can be transmitted to the vendor. Therefore, when a PO is created, it is assigned a release indicator that blocks it from being outputted in message form.
The Released indicator must not be selected for this indicator.
o     Release indicator for released status
This indicator is assigned to the PO when it is released.
The Released indicator must be selected for this indicator.
Release strategies
Create a release strategy for your release group and assign your release codes accordingly.
·     Release prerequisites
With the release prerequisites , you specify the order in which the individual release points (individuals or departments) represented by the release codes may release the document.
Example
The following table shows release prerequisites for a strategy with four release codes.
Code/Release prerequisite
          01     02     03     04
     01     -
     02          -
     03               -
     04                    -
In this release strategy, the codes 01, 02, 03, and 04 must successively release the purchase order.
Read the table from left to right. For instance, the third line for release code 03: For code 03, release via code 01 and code 02 is a prerequisite. That is to say, the PO must be released via codes 01 and 02 before it can be released via code 03.
·     Release statuses
Here you specify the status a PO has after certain release points have effected release.
Specify which release indicator/status a PO is to have after having been released via a certain release code.
·     Classification
In classification, you maintain the values assigned to the characteristics. Via the characteristics and their values, you specify the POs to which your release strategy is assigned.
Maintain values (individual values or intervals) for your characteristics.
Example
Two characteristics and their values have been maintained in classification for release strategy 'EA':
- Document type - 'NB - standard purchase order'
- Total value - above $10,000
All POs with the document type 'NB' and a total value in excess of $10 ,000 are thus subject to a release procedure with the release strategy 'EA'.
·     Release simulation
The release simulation function enables you to check which status a PO will achieve with your release strategy if release is effected by a certain release point.
Choose "Simulate release" and release the document with the desired release code by double-clicking. The system shows you which status the PO now has as a result of this release.
Workflow
Assign a processor ID to your workflow-relevant release codes. The processor (member of staff responsible for processing the document) will then receive a work item when he or she is required to effect release.
You can assign a processor ID either directly or indirectly:
o     Direct processor assignment:
Enter a user name.
o     Indirect processor assignment:
Enter a job, for example, or a position. At runtime, the system will then determine the member(s) of staff responsible for processing the document.
Customer exit
Customer exit M06E0005 enables you to define your own role resolution which determines the person responsible for releasing purchasing documents in workflow.
Further notes
Further information on how to set up a release procedure linked to workflow is available via the menu options Help -> Application Help.
Check Release Strategies
In this step, you can check whether the basic settings for your release strategy are complete and correct.
Checks
The following checks are carried out for purchasing documents:
·     Basic checks
The system checks whether the necessary release groups exist in the system. For example: Whether a release group has been deleted even though an associated release strategy still exists.
·     Checks regarding release groups and release classes
The system checks whether the release groups and the assigned classes have been maintained correctly. For instance, whether
o     A class has been assigned to the release groups and whether it exists in the system
o     Characteristics - which exist in the system and are linked to the communication structure - have been assigned to the class
o     A customer exit must be maintained for a characteristic
·     Checks regarding release codes
The system checks whether the release codes have been maintained correctly
·     Checks regarding release indicators
The system checks whether the release indicators have been maintained correctly. For example: Whether release indicators exist for the statuses "Blocked" and "Released".
·     Checks regarding release strategies
The system checks whether the release strategies have been maintained correctly. For example, whether:
o     Release codes have been assigned to the release strategy
o     The relevant release indicators have been assigned to the initial and final statuses of a release strategy
·     Checks regarding link to workflow
The system checks whether the link between your release procedure and workflow has been maintained correctly. For example, whether:
o     A processor (member of staff responsible for processing) has been assigned to a workflow-relevant release code and is defined in the organizational plan
o     A customer exit is necessary for the role resolution
Result
The result of these checks is displayed in a log. Further information is available in the Customizing activity under Help -> Application Help.
Activities
1. Start the check by performing the Customizing activity.
2. Check whether any error or warning messages are displayed.
3. If necessary, correct your Customizing settings for the release procedure.
4. Re-run the check after making corrections.
Rewards if Helpful
Regards
Sanjay L

Purchase order total value

Similar Messages

Maybe you are looking for