BAPI_PO_CREATE1 pricing date issue

Hi
I am creating the PO using BAPI_PO_CREATE1 but its picking pricing date as delevery date.
from POSCHEDULE.
Can anybody guide in this regards. what parameter are supposed to pass for the getting pricing date.
Regards
Sagar

Hi Eric,
Thanks for your reply.
In the BAPI we are passing
          poheader          = ls_poheader_bapi
          poheaderx         = ls_poheaderx
          testrun           = iv_testrun
          no_authority      = lc_check
          no_price_from_po = lc_check
        IMPORTING
          exppurchaseorder = lv_exppurchaseorder
          expheader         = ls_expheader
        TABLES
          return            = lt_return
          poitem            = lt_poitem_bapi
          poitemx           = lt_poitemx
          poschedule        = lt_poschd_bapi
          poschedulex       = lt_poschdx
          poaccount         = lt_poacc_bapi
          poaccountx        = lt_poaccx
          pocondheader      = lt_pocondheader
          pocondheaderx     = lt_pocondheaderx
          pocond            = lt_pocond_bapi
          pocondx           = lt_pocondx
          polimits          = lt_poesh_bapi
          pocontractlimits = lt_poesuc_bapi
          poservices        = lt_poser_bapi
          posrvaccessvalues = lt_poserac_bapi
          poservicestext    = lt_postext_bapi
          potextheader      = lt_pohtext_bapi
          potextitem        = lt_poitext_bapi.
here in this case its not picking the pricing date.
Regards
Sagar

Similar Messages

Pricing date issue

Hello All,
We have an issue with the Line item pricing date.
In our project we are using the supersession functionality; we have one sales order with header pricing date ex: 25.12.2008 with some line items, for line item 10 we have created superesession material on 01.01.2009 with other material and maintained the pricing condition records validity date same as 01.01.2009.
We maintained in a way that if the material is not available and superseded material is available one job will run and creates the new line item with superseded material and copies the all information from the old line item. Here the problem is it copied the old material pricing date as 25.12.2008 due to this the new line item price is not calculated because the condition record is available from 01.01.2009 and it is disable mode.
Can any one give an idea how to solve the above issue.
Thanks and Regards
Srinivas Kapuganti

Hi Srinivas,
reading the answer above, there are 2 ways to solve your problem:
1) Modify the logic that determines the pricing date
2) Use the pricing reference material field (i.e. workaround)
Unfortunately in the landscape currenly i'm working, I haven't installed APO... So I cannot make any tests in a similar landscape.. however I can try to suggest to you something...
Concerning the "idea" N. 2 you have:
A) To check (from a "business point of view") if superseeded material and the new material have the same price.. I think so.. In the past I've worked as consultant in an A&D company and we have implemented supersession.. Usually, from a "commercial point of view" no impact on pricing must be "charged" to the customer because "supersession". So, usually, the superseeded material and the new one has the same pricelist...
B) From a "technical" point of view, try change manually the sales order updated by APO BOP and fill (manually) the field VBAP-PAMTN (item detail, tabstrip "Sales B") and, please, check if SAP determines the correct price condition record.
C) If test in point B is "ok".. I think that when BOP try to change the sales order, the userexit move_field_to_vbap will be called (include MV45AFZZ).. If you are able to understand to which "old" SO item is referred the new one, you can use this exit to fill VBAP-PMATN field of the new item with the superseeded material code (the old one)....
Advantage:
1) You don't have to change the program called by RFC from APO (maybe it requires an out of standard solution? I don't know..). You have "only" to implement an userexit..
2) SD pricing date will be, also for the new item, the 25.12.2008; but, in this case, SD will be able to find (via PMATN field) the pricing condition record linked to the superseeded material. This solution is Ok if hypotesis in point A) is correct. Otherwise it make no sense.
Sorry for quite long answer. Hope this help.
Have a nice day - Massimo

Issue regarding condition pricing date as system date for some condition types in sales order

Hi
I have already created a sales order on 30.04.2014. Today I am adding new line item to sales order in VA02 transaction. in this order new line items condition pricing date for conditions JEX2,JECX should show as 12.06.2014. But currently it is showing as 30.04.2014. I need condition pricing date as system date for above conditions.
Regards
prashant

Hi
When I am changing pricing date VBKD-PRSDT in sales order header . It is changing the condition pricing date for all. Sales order is created on 04.06.2014. I have added line item 150 on 14.06.2014.
After adding line item 150 , there I have changed the pricing date as 14.06.2014. in sales A tab of item 150. But still it is taking from Sales order header date as 04.06.2014 for all conditions. But my requirement is for line item it should take as system date for some conditions like JEX2,JECX& JA1Y but for other conditions it will take as Order creation date. Please suggest. I have also attached screen shot below. please go through it.
Regards
PK
Sales order header change mode VA02
Here pricing date VBKD-PRSDT = 04.06.2016
Item change mode
I have added new line item 150 on 14.06.2014
Changed the condition pricing date to 14.06.2014 & saved
After saving I have gone to Va02 screen of line item 150
& there I have gone to condition pricing date field from item condition tab
for JEX2 condition type but still here condition pricing date is showing as
04.06.2014 as below.
Condition pricing date
My requirement is like this
For some particular conditions like JEX2 condition pricing date will take as system
date instead sales order creation date when I will add a new item 150 on
14.06.2014.but for other conditions it will show as order creation date for the
same line item 150 .

How to change the pricing date inthe conditon record access details

Hi Team,
Please help to solve this issue.
When we create a sales order, pricing date will update as creation date and the same date will appear in the condition records access details for all the respective condition type.
In case of sales order is created with reference to Contract then pricing date will update same as from the contract pricing date.
for examaple contract created on 01.01.2014 for the same day if we create the sales order with reference contract then pricng date will update as 01.01.2014 in the sales order.
If we create the sales order example today 19.05.2015 but stil pricing date will update as 01.01.2014 (due to same date available in the contract)
Now my requirment is for one of the condition type ex ZXXX this pricing date should update as sales order creation date (Not all the condition types) in the condition record access.
Please check and let me know ho to solve this issue.
Thanks in Advance.
MK.

Hi MK,
When we define a price condition in customizing, we have field Pricing date, with the following entries available:
‘ ‘   Standard (KOMK-PRSDT; tax and rebate KOMK-FBUDA)
A    Date of services rendered (KOMK-FBUDA)
B    Price date (KOMK-PRSDT)
C    Billing date (KOMK-FKDAT)
D    Creation date (KOMK-ERDAT)
E    Order date (KOMK-AUDAT)
Use E.
Regards,
JM

Control Sales order Pricing Date with Delivery GI Date

Is it possible to have a control that ensures the Actual GI date in a delivery is not more than a number of days from the sales order pricing date?

Hi,
To have restriction in actual GI date in transaction VL01N . Please find the user exit for VL01N , you can use one which are marked as bold . Kindly take the help of abaper to put the validation or logic as required.
V02V0001   - Sales area determination for stock transport order
V02V0002   - User exit for storage location determination
V02V0003   - User exit for gate + matl staging area determination
V02V0004   - User Exit for Staging Area Determination (Item)
V50PSTAT - Delivery: Item Status Calculation
V50Q0001   - Delivery Monitor: User Exits for Filling Display Fields
V50R0001    - Collective processing for delivery creation
V50R0002    - Collective processing for delivery creation
V50R0004    - Calculation of Stock for POs for Shipping Due Date List
V50S0001    - User Exits for Delivery Processing
V53C0001    - Rough workload calculation in time per item
V53C0002    - W&S: RWE enhancement - shipping material type/time slot
V53W0001   - User exits for creating picking waves
VMDE0001 - Shipping Interface: Error Handling - Inbound IDoc
VMDE0002 - Shipping Interface: Message PICKSD (Picking, Outbound)
VMDE0003 - Shipping Interface: Message SDPICK (Picking, Inbound)
VMDE0004 - Shipping Interface: Message SDPACK (Packing, Inbound)
Hope this will help you to resolve your issue!!!!
Regards,
Krishna O

How can I deactivate the pricing date and material pricing group in VA01?

Hello All,
How can I deactivate (output only) the pricing date and material pricing group field in VA01/2, VA21/2, and VA41/2? What user exit can I use? Thanks in advance...
PeeJay

You can use the t.code SHD0, choose your transaction variant here, further choose your screen variant.
Next select your screen variant and in the Menu bar select Variant> change with processing>Make repairs in foreign namespaces only if they are urgent> Continue(Enter)>again 'enter'>Object can only be created in SAP package>continue(enter)> Exit and save >This variant contains other screens, adopt these as well?>enter>enter> scroll down to the entry 'pricing date' or VBKD-PRSDT make the necessary changes and save.
The system will prompt to assign a package and request enter the necessary values.
Your issue is sorted!!
Regards,
PATHIK

Pricing condition in Billing document (Pricing Date)

Hi Gurus,
I have a sales order which is created on 10.01.2012, the pricing date in the sales order is the same (10.01.2012). The Delivery was created on 22.02.2012 and Actual GI date is also 22.02.2012.
Now when I am creating the billing document, the pricing condition value is showing as '0'. I checked the pricing analysis and found that the validity of the base price condition Z001 was from 10.01.2012 till 14.01.2012 in the sales order.
As the Actual Goods Issue date is taking as the 'Billing date' as well as 'Pricing Date' , the system is not able to find a valid condition type as on 22.02.2012 (GI date). The pricing type in copying control of Delivery to Billing is 'C - Copy manual pricing elements and redetermine the others'.
So I would like to know your opinion on the following.
1) Can I create the billing document using VF01, manually change the pricing date as 10.01.2012 and do the price update using rule C? Will it fetch the price based on the pricing date?
OR
2) Maintain the condition type Z001 for the GI date and do the billing?
Please let me know which is the best way to adopt?
Regards,
SAM

Hello,
If you have necessary authorization to change the Pricing Date in Invoice, please go ahead.
Change the Pricing date in Invoice, go to Conditions tab & update the Pricing. System will fetch Condition Records as on that date.
Hope this helps,
Thanks,
Jignesh Mehta

InterCO Billing for Stock - Pricing Date

hi,
I have the following problem:
We do an interco sale from the purchase order to delivery to goods issue to billing,
Sometimes and order is placed a couple of moths ago and we need to adjust the price to that date on the Interco billing document, however, the price date the billing document uses is the Actual Goods Issue date from the delivery. The block is greyed out and cannont be changed.
Does anyone know how we can change the pricing date on the item to pick up the correct pricing.

hi,
Our intercomapny process starts with a purchase order. that purchase carries to the delivery the Planned goods issue date. the delivery occurs some time after and the actual goods issue date is captured. the billing document takes the Actual Goods issue date. We want to be able to change that.

Billing date as the Pricing date

Hi,
When im updating the Invoice using VF02 (Still the accounting entries are not posted), i want to change the Pricing date as the billing date.
What is the pricing type i should select to update the prices according to the billing date.
Thank U,
Uwanthi

hi,
Click on the update button in the conditions tab in billing and select carry out new pricing. this shoud resolve your problem. But Im usat warn you that you might loose out the valeus for the conditions which has been entered manually or in certain even some condition records maintained with some specific access could have issues.
Anyways, carryo ur new pricing is the solution for you problem.
If you want the same to happen every time, you can maintian the pricing type for the above mentioned one ( I think it is B) at tyhe item level in copy control settings
Thanks & regards,
Nithin

Pricing date change does repricing...

Hi,
When we change a Pricing date manually, system does the repricing.. (that is carry out new pricing). Here the manually entered value has been erased.
My requirement is
When I change the pricing date (any field which does repricing)
it should do " copy manual pricing elements and determine others" pricing type.
help urgently needed on any userexit or oss note

Friend,
I am in position to expalin the situtation, we are creating pricing procedure for warranty not for sale.
Example, when my client sell their car, they will give 2yrs 2000 miles warranty. When the final customer report the dealer
with in 2 yr or with in 2000 miles, the dealer will repair the car. After the repair, they will create claim in their legacy system and send to my client.
Here they can claim material they replaced, and labor hour they spend and some misc charges.
Issue, when they create claim in their system immd it creates in my client r/3. During that time it takes the pricing date is current system date. once the claim submitted we are changing the pricing date by using some function.
This time standard sap does the carry out new pricing (B) but we want C.
help needed

Pricing Date determination

2. is it possible to have a calculation rule for each customer. For example Customer A pricing date based on delivery date; Customer B pricing date based on goods issue I date

Hi,
The pricing date is proposed based on the setting you make in the Sales document configuration. ( T code : VOV8)
You have a field" Prop.f.pricing date " in the Requested delivery date / pricing date / purchase order date segment.
Then you can choose the follwoing options:
Blank - Indicates the current date as the pricing date
A - Indicates the date based on the requested delivery date
B - Indicates the date based on the order validity start from date
And the pricing in the billing document is copied from thte sales order / Delivery document..
It again depends on the setting u have in the copy control from order - billng or delivery - billing.
In the copy control, in the item settings you have two fields relavant for this.
One is pricing source and the other is pricing type.
The pricing sources are generally the order. But if you want you can change it to other values mentioned in the drop down,
but this values have no effect if the pricing type is B.
Any other value other than B in the pricing type will take the reference document price mentioned in the pricing source field.
but for the pricing type B. The new price is determined in the billing order.
Prerequisites
To activate automatic determination of the pricing date or the settlement date, you must make the following settings in Customizing:
Definition of the date rule
When you define the date rule, you specify a sequence of shipping deadlines (for example, end of transportation planning or planned start of loading) which are used to determine the pricing date or the settlement date. The sequence of the deadlines reflects their priority for access. If there is no value for the first deadline, then the next deadline is checked, etc.
You make these settings in Customizing: Logistics Execution ® Transportation ® Shipment Costs ® Basic Shipping Functions ® Define date rules.
Assigning the date rule
In the definition of shipment cost item categories, you can assign a date rule to the pricing date and one to the settlement date.
You make these settings in Customizing: Logistics Execution ® Transportation ® Shipment Costs ® Shipment Cost Document ® Shipment Cost Types and Item cats ® Define item categories.
Regards,
Saju.s

DP90 pricing date missing in DMR item data

Background: Im implementing sales pricing discounts for sales orders generated from service orders via RRB. Currently, we create service orders to capture costs then use RRB (DP90/DP95) to create DMR documents to bill customers for the services. Costs are transferred to DMR as condition types EK01 actual costs.
Issue: In DP90/DP95, if I leave the pricing date blank..the DMR creates with a blank item pricing date. The DMR header pricing date is populated with current date. Since the item pricing date is blank, the system does not find the discount condition records.
F1 help on the DP90/DP95 field says "If you want to use the internal date determination facility in SD, leave the field empty."
If I create the DMR manually in SD, the pricing dates determine correctly...nothing remains blank. Our SD doc type config uses a "blank" for the pricing determination (current date).
My concern is that end users will forget to enter the pricing date in DP90/DP95 resulting in the customer being overcharged. Are we missing config somewhere? As an alternative, is there a way to make the pricing date on DP90/DP95 a required field? Since this only happens from DP90/DP95...Im trying this forum first.
All help is greatly appreciated.
Allison

Hi,
Make it required field on initial screen of DP90 by screen & transaction variant
T-code SHD0
Put t-code DP90 and click on tab screen variant and maintain below
Screen variant       ZDP90
Program              SAPLVPK_GUI_INTRO
Screen               300
Then click on create button then initial screen will appear then click on expenses or sales price then FILED SCREEN will pop up
Make PRICING DATE as REQUIRED and click on exit & save again save it.
Come back and click on tab TRANSACTION VARIENT
Put Transaction Variant - ZDP90 and click on change icon
put screen variant ZDP90 enter and save
If you want test is then test by clicking TEST (F8)
Now assign this transaction varient in SE93
Put Transaction Code - ZDP90 and click on create
Then enter short text and select option 4 i.e TRANSACTION WITH VARIANT
Then enter
Transaction             DP90
Transaction variant     ZDP90
And save
Now instead of DP90 use ZDP90 in this pricing date will appear as required field.
Kapil

***Price Determination (Pricing) Date Control

Hi Experts,
The client requirement is that it has a contract maintained for different months with different prices. PO is created for a certain date and price. But they want to do the GR with a later date may be after 5 months for the service they have received. They want to post the GR in the open period but the price should be picked up depending on the contract price maintained for that date in past.
In contract and in Vendor we have a field called Price Determination (Pricing) Date Control which determines which date is to be used for price determination (pricing) purposes.
My issue is if i use manual which is # 5 in contract and in Vendor still when i do the GR i am getting the price with the present posting date or the present date which has been maintained in the contract. Where should i maintain the manual date on GR so that my contract price gets picked up.
Thanks for your support.
Mavrik

Dear Mavrik,
The price always follow the date maintained in the price date field in the condition control tab at ME21N during
creation of the PO. If you want during GR, the price follow a specific date, please kindly check and change
again the date in the particular PO at the same tab and at the condition tab, click the update button after
change the date.
Best Regards,
Ian Wong Loke Foong

HELP!! - Pricing Date Control error

Hello experts,
I have a problem with pricing date control.
I would like to set Pricnig date control=5(GR Date)in Vendor master.
However, if I do so, I get an error in MIGO-GO said"Transaction cannot be posted due to errors in price determination:MSG no. ME573"
I don't have a problem if I set Pricing Date Control anything other than "5".
Where should I customize(IMG) to fix this problem?
This is very important, so I would like to rewards points to those who give me valuable answers.
Thanks in advance,
YO

Hi,
Please check info record Pricing date control and Purchase order Price date control in Item details>more functions
Following will help you tounderstand more on this
In the automatic price determination process, the price can be calculated as at the document date of the PO, or as at another date (such as the current days date, the delivery date, or the goods receipt date). You can specify the date to which the price that is determined relates at the following points:
In the vendor master record, in the Pricing date control field, if you wish to use the same price determination date for all a vendors materials.
In the purchasing info record, in the Pricing date category field, if you wish to use a different pricing date for a certain material supplied by a particular vendor.
The value in the purchasing info record takes precedence over the value in the vendor master record.
In the purchase order, in the Pricing date category field (found via Item > More functions> Additional data).
The value from the info or vendor master record is preset when a purchase order is created. However, this is only used if you change it in the purchase order and carry out a new price determination process.
The pricing date category in the PO takes precedence.
Example:
In the info record, you have specified that the price determination process is to be carried out with the conditions that are valid on the delivery date (pricing date category 2). Furthermore, you have created two validity periods (from 04. 01.1997 until 04. 31.1997 and from 05. 01.1997 until 12. 31.1997), each with different conditions.
You create a purchase order with the delivery date 05.05.1997. The pricing date category from the info record is adopted. In the course of the price determination process, the info record conditions from the validity period 05. 01.1997 until 12. 31.1997 are then adopted.
If you wish to adopt the info record conditions from the first validity period in the purchase order, you must change the pricing date category in the PO to blank and carry out a new price determination process.
Hope this will help to resolve your issue
BR
Diwakar
reward if useful

Pricing date category

Hello coworkers,
Is there anyone use pricing date category 5 in purchase order before?I found when I use this selection, the goods receipt price will incude tax amount together with the goods net price, therefore, the goods cost is containing tax amount. While per accounting report, the tax amount should not be calculated into cost of goods. Can anyone help to put some light on this issue?Thanks a lot
Joanna
MM consultant
E-mail:[email protected]

Hi,
Pricing date category is noting to do with tax calculation. This indicates 5 help to post condition price which is valid on GR date.
Issue could be in Tax code. Check tax code I guess in your case tax type (sales tax) is inventories by key NVV. Or Account key which you have define for tax is inventories.
Thanks
Yogi

BAPI_PO_CREATE1 pricing date issue

Similar Messages

Maybe you are looking for