To change vendor no for condition types using BAPI_PO_CHANGE

Hii,
how to change vendor no for certain condition types using BAPI_PO_CHANGE.
Is it possible .
Any parameter is there.
Plz help urgent
Title edited by: Alvaro Tejada Galindo on Jun 12, 2008 5:23 PM

Hi,
   It is possible.
wa_pocond-vendor_no = wa_konv-lifnr.
wa_pocondx-vendor_no = 'X'.
   wa_pocond-condition_no = wa_konv-knumv.
    wa_pocond-itm_number = wa_konv-kposn.
    wa_pocond-cond_type = wa_konv-kschl.
    wa_pocondx-condition_no = wa_konv-knumv.
    wa_pocondx-itm_number = wa_konv-kposn.
    wa_pocondx-cond_type = 'X'.
    wa_pocondx-change_id = 'U'.
    APPEND wa_pocondx TO it_pocondx.
    CALL FUNCTION 'BAPI_PO_CHANGE'
      EXPORTING
        purchaseorder                = wa_konv-ebeln
      POHEADER                     =
      POHEADERX                    =
      POADDRVENDOR                 =
      TESTRUN                      =
      MEMORY_UNCOMPLETE            =
      MEMORY_COMPLETE              =
      POEXPIMPHEADER               =
      POEXPIMPHEADERX              =
      VERSIONS                     =
      NO_MESSAGING                 =
      NO_MESSAGE_REQ               =
      NO_AUTHORITY                 =
      NO_PRICE_FROM_PO             =
    IMPORTING
      EXPHEADER                    =
      EXPPOEXPIMPHEADER            =
     TABLES
       return                       = it_return
       poitem                       = it_poitem
       poitemx                      = it_poitemx
      POADDRDELIVERY               =
      POSCHEDULE                   =
      POSCHEDULEX                  =
      POACCOUNT                    =
      POACCOUNTPROFITSEGMENT       =
      POACCOUNTX                   =
      POCONDHEADER                 =
      POCONDHEADERX                =
       pocond                       = it_pocond
       pocondx                      = it_pocondx
      POLIMITS                     =
      POCONTRACTLIMITS             =
      POSERVICES                   =
      POSRVACCESSVALUES            =
      POSERVICESTEXT               =
      EXTENSIONIN                  =
      EXTENSIONOUT                 =
      POEXPIMPITEM                 =
      POEXPIMPITEMX                =
      POTEXTHEADER                 =
      POTEXTITEM                   =
      ALLVERSIONS                  =
      POPARTNER                    =
      POCOMPONENTS                 =
      POCOMPONENTSX                =
      POSHIPPING                   =
      POSHIPPINGX                  =
      POSHIPPINGEXP                =
      POHISTORY                    =
      POHISTORY_TOTALS             =
      POCONFIRMATION               =
    COMMIT WORK AND WAIT.

Similar Messages

Unable to manually change the amount for condition type PB00

Hi Gurus,
My client is using ECC5.0.
Here when I try to change the amount for condition type PB00 using transaction ME22N, I am not able to change the value. I donu2019t get any error, but as soon as I change the value and press Enter the system replaces my entered value with the original value.
Confusing part is that I am able to change the amount of condition price PB00 manually using transaction ME22. I donu2019t have any such problems there.
Also I am able to manually change the amount of condition type PBXX using ME22N.
Only in the case of PB00, if I use ME22N to manually update the amount I am not able to change it.
Kindly help me, to find a reason as to why this could be happening, and correcting if possible?
Thanks in advance,
Imran

Hello Imram,
The purpose of maintaining 2 condition types ie PB00 and PBXX in a pricing procedure is that PB00 is automatic gross price determination and PBXX is manually giving gross price.
If you go to T.Code : M/06 and check the condition types, you can see that PB00 will be having an access sequence but not PBXX.
So if you have to manually give the gross price, you have to use PBXX.
Regards

Change accural key for condition type

Hi,
The accural key for condition type " special addition custom duty" is maintained wrongly in our Prd system .As a result wrong GL is getting posted.
We want to change the accural key for this condition type.
Not sure of the implications....
There will be a problem with the existing Purchase Orders for which GR posted and Invoice pending.
If the new PO is created, the condition type may be fetched through the Info records. Info records will fetch the last purchase order and if the last PO is created before the changes done then the old accural key may appear in the new PO.
How to handle this...?
What is the standard process to handle the mistakes in the condition types?
Regards,
Rajesh Satope

Hi Rajesh Satope,
For "clean" open PO's (no GR or invoice) you can obtain the new codition type settings by applying "Update prices" at the bottom of the conditions screen. I am not sure though how can you do it for many PO's at once.
For PO's with partial transactions posted, I believe you will have to complete them with the old setting, i.e. the balance on the accrual account booked via the GR shall be cleared on the same account by the invoice - so you shouldn't run "Update prices" for such PO. I think even SAP standard prohibits this.
BR
Raf

Can we make default vendor code for condition type

We have created a condition type for cess. While creating with this condition, by default system should select a particular vendor. How to make default Vendor for that particular condition type. So that users cannot make mistakes while creation PO with the condition type.

Hi Guru,
I have one doubt. if access sequence is not defined for this purchase condition then, in that case the txn MEK1 will not work. Then in that case how to use MEk1 transaction?
Could you please explain me in detail as to how to go about it & meet this requirement?

I want to change the amount in condition sheet using bapi_po_change

hi experts:
i want to use the bapi_po_change to change the amount in condition sheet in me23n.
the parameter i set is below:
DATA:
lt_return LIKE bapiret2 OCCURS 0 WITH HEADER LINE, "返回内容
lt_poheader like bapimepoheader,
lt_poheaderx like bapimepoheaderx,
ls_pocondheader like BAPIMEPOCONDHEADER occurs 0 with header line,
ls_pocondheaderx like BAPIMEPOCONDHEADERX occurs 0 with header line,
ls_pocond like BAPIMEPOCOND occurs 0 with header line,
ls_pocondx like BAPIMEPOCONDX occurs 0 with header line,
lt_POITEM LIKE BAPIMEPOITEM OCCURS 0 WITH HEADER LINE,"
lt_POITEMx LIKE BAPIMEPOITEMx OCCURS 0 WITH HEADER LINE,
l_flag(1),
g_text(50) TYPE c.
CLEAR: l_flag.
lt_POITEM-po_item = '00020'.
lt_poitem-NET_PRICE = '15.10'.
APPEND lt_POITEM.
CLEAR lt_POITEM.
lt_POITEMx-po_item = '00020'.
lt_POITEMx-po_itemx = 'X'.
lt_POITEMx-NET_PRICE = 'X'.
APPEND lt_POITEMx.
CLEAR lt_POITEMx.
ls_pocond-condition_no = '0000006887'.
ls_pocond-itm_number = '000001'.
append ls_pocond.
ls_pocondx-condition_no = '0000006887'.
ls_pocondx-itm_number = '000001'.
append ls_pocondx.
CALL FUNCTION 'BAPI_PO_CHANGE'
EXPORTING
purchaseorder = '4500000002'
TABLES
return = lt_return
POITEM = lt_POITEM
POITEMx = lt_POITEMx
POCOND = ls_pocond
POCONDX = ls_pocondx.
but it doesn't work ,it goes to change the net price, how should i set the parameter? hunger for ur advice!!

Hi,
are you using BAPI_TRANSACTION_COMMIT or a COMMIT WORK after the bapi call?
Have a look at the code of fm ME_CCP_TPO_PRICE_CHANGE maybe that can help.
Best regards
Edited by: pablo casamayor on Jun 6, 2008 10:15 AM

Condition Types used in a particular country

Hi Experts,
I am trying to pull a report of changes made to the condition types using VK13. Before doing this, I would like to know what are the condition types used for a particular country. How can I find out the condition types used for a particular country. Please advise.

Hi Murukan,
As above said we will not maintain condition record for country,until we select the country in our access sequence.
You know the changes made to condition type by the table CDHDR and CDPOS
go to SE16N give the table CDHDR there in TCODE filed give VK12 you will get all changed information regarding that and get the
value in filed CDHDR - OBJECTID pass the same into CDOPS - OBJECTID you can get specific record information.
Check and revert
Regards
Ram

Account determination for condition type

Hi Guru,
I have requirement where I need to assign G/l account in VKOA for condition type used for discount and markup same time. I know I can aasign trade discount to this condition type but how about markup. can we assign two diffeent account to same condition type based on uses.
Thanks

This is pricing conditions not condition type like KOFI. The pricing condition are like base price, discount , markup, special custmer discount, ect. You can see these contions in sales order under condtion tab. My issue is there one condtion that user use some time for discount and some for mark up and requirement is when this condition is used for discount, it post to one account and if used for mark ,should go to different accoount. In VKOA sequence 501, we can only assign one account to one condition. if some one know how to assign two G/Ls to one condition .

Condition type used for invoice list

Hello Gurus,
following condition type used for invoice list, why do they exit in invoice list:
RL00 MW15. LR00 RD01

Hi,
Please go through the below document
When you work with invoice lists, you need to be familiar with the following concepts:
Prerequisites for invoice lists
Relationship to Pricing
Structure of an Invoice List
Changing header and item data
Integration with financial accounting (FI)
Prerequisites
You can only process invoice lists if the following prerequisite data is defined by your system administrator in Customizing for Sales:
Condition type RL00 (factoring discount) must be maintained and, if required, also the condition type MW15.
An invoice list type must be assigned to each billing type that you want to process in invoice lists. The standard version of the SAP R/3 System includes two types of invoice lists: LR for invoices and debit memos, LG for credit memos.
Copying requirements must be defined (for example, the payer, terms of payment and other fields that must be identical in the documents to be included in the invoice list)
In addition, before you process an invoice list, you must maintain the following master data:
A customer calendar must be defined, specifying the time intervals or dates on which invoice lists are to be processed.
The customer calendar must be entered in the Billing Sales Area view of the customer master record.
Pricing condition records for the condition type RL00 and, if necessary, (e.g. in Germany) the condition type MW15 must be maintained.
Output condition records for condition types LR00 and RD01 must be created.
Relationship to Pricing
The system processes factoring discounts in invoice lists in exactly the same way as other kinds of pricing elements. The data for the factoring discount is stored in condition records. Controlling during document processing is carried out via condition types, pricing procedures and access sequences. This control data is defined in Customizing for Sales by your system administrator.
For further information, see Conditions and Pricing.
Structure of an Invoice List
An invoice list represents an individual billing document. It consists of a document header and document items. Each item represents a billing document that you have included in the invoice list. The header contains an overview of summary information, such as the net value of all documents in the invoice list, the value of the factoring discount, details of taxes, and so on. It also contains information on partners and output.
Changing Header and Item Data
You can change some of the header data - for example, the billing date - when you process the invoice list. You can change an item - either an individual or collective invoice - and display document details. However, you cannot change any data in individual billing documents once they are part of an invoice list.
It is possible, however, to make certain global changes to output in all items in an invoice list.
For further information on output, see Communication in Sales and Distribution Processing.
Integration With Financial Accounting (FI)
The documents that you want to combine within an invoice list must already have been billed and forwarded to Financial Accounting. Here the billing documents intended for an invoice list are blocked for normal dunning transactions.
The dunning block on FI documents is lifted as soon as you create an invoice list and transfer it to FI . The system then calculates the new dunning date for the invoice on the basis of the invoice list date.
In addition, the system enters invoice list numbers in the FI documents as reference numbers. Invoice list numbers can then be entered for incoming payments.
When you save the invoice list, the system automatically creates an accounting document for the factoring discount and possible taxes and posts it to the corresponding G/L account in FI.
Regards,
Murthy

Standard Condition type used for Manual freight at item level

Hello Gurus
Can you please tell me the standard condition type used for entering freight manually at header as well as item level.
Warm Regards
Prashant Joshi.

Prashanth,
The freight Conditions that we use in Sales are two types
HD00 - Header Level, wherein we have no access sequence
KF00 - Item level, Wherein we have access sequence KF00 - Freight
But you want the condition types to be maintained manually, then you need item details screen of the respective condition type HD00/KF00 using Tcode V/06.
Inside that Manual entry as "C". Similarly you need to maintain or activate "Manual" Indicator in pricing procedure. Then you can enter the freight Manually.
Note:
The difference In applying at the header level and item level is if you enter freight value at the header level it is applicable to all items in the item level. But if you want to apply freight we can give freight to each item or selective item.
Regards
Sathya

Condition type used for scrap

hi,
what is the condition type used for scrap in Standard SAP.?Assured points
Best regards,
R.Srinivasan

Dear Srinivasan
Follow the below process:-
1) Go to V/06, either copy the standard or create a new by naming ZTCS and maintain the following:-
- Cond. class::::::::::A
- Calculat.type::::::::A
- Access seq.::::::::::K004
- Manual entries:::::::D
- Item Condition:::::::X
- Text DetPrc::::::::::04
2) Again in V/06, create one more condition type (say ZECT) for Edu.Cess on TCS for which the same values can be maintained as like ZTCS
3) Go to OV34, create an Account key for TCS, say ZTC and ZET for Edu.Cess
4) Go to VK11, input the condition type ZTCS and maintain the required TCS percentage (the combination which you can maintain is for Sales Org / Dis.Channel / Material or as per the requirement demands you). Similarly, you have to maintain the required percentage for Edu.Cess also in VK11
5) Now go to V/08, create a new pricing procedure exclusively for scrap sales and maintain these two condition types there with respective Account Keys
thanks
G. Lakshmipathi

Different vendors in freight condition type error in MIRO

Hi,
We are using different vendor in condition type for import purchase order as given.
Ordering Vendor - 800000
Custom Vendor - 900000 in condition type
Freight Vendor - 700000 in condition type
While i am doing Goods Receipt, In the Freight tab only ordering and freight vendor is showing. And at the time of MIRO all three vendor are showing for selection.
Question: So is there any restriction for condition type. And if i change vendor at condition type after MIGO what will be effect on MIRO.
We are using GR Base Invoice verification.
Thanks in Advance.

Hello Venki,
While doing Customs MIRO, please select from the drop down as 'planned delivery cost' option. Once you select this, then you can find your customs vendor flowing from PO.
Hope this helps.
Vikas.

Updating Vendor of Freight Condition Type in STO

Hi,
I am facing a problem in updating KOMP-LIFNR in my program. I have below scenario
I have created a Z program which gets all materials from mchb and creates a STO order thru a BAPI_PO_CREATE1. Anyway STO is getting created but i am facing a program to update a freight condition type. I need to LIFNR(Vendor) in freight condition type.
Pls help is how to update is there any bapi to update.
Regards,
Sreekanth

Hi
We dont have any fields in the BAPI_PO_CREATE1 to directly input the Freight vendor , But by maintaining the freight vendor in the purchase infor record will update the Conditons in the PO at the time of creation of the PO.
You can also acheuive this by using the user exit enhancement SAPL2012
Exit : EXIT_SAPL2012_001.Customer Exit for Creating a Purchase Order in Enjoy Using BAPI_PO_CREATÊ1
You can chek out using SMOD.Please take the help of ABPERs to develop the code as per the requirement.
Award points if useful
Thanks & Regards
Kishore.

Currency conversion issue for condition type

Hello,
I am creating two invoice document.
1. Customs Invoice (ZCDS)
2. Inter company invoice.(IVA)
both the invoices should be similar. Same pricing procedure is used to create both the documents but in Customs invoice YUMU condition type is not getting converted whereas in IVA the condition type is getting converted. Can anyone tell me the possible reason for this?
ZCDS
IVA
Regards,
Jagjeet

Hi Jagjeet,
For IVA invoice type -(For condition type- YUMU)
Below highlighted part of code is changing KSTEU from 'E' to 'C' for IVA invoice using std prog RVIVAUFT.
For ZCDS Invoice Type -(For condition type- YUMU)
Program RVIVAUFT is not called since ZCDS is not trigerried using Output type unlike IVA.
Hence KSTEU is not getting updated from 'E' to 'C' in case of ZCDS.
To solve your problem write code in User exit - userexit_pricing_copy to change konv-ksteu to 'C' for YUMU condition type at runtime.This will definately solve your problem.This will ensure you get correct/same condition value for IVA and ZCDS...:)
Regards,
Vikas Mulay.

Authority check in for condition type

Hi
What do you mean by an authority check on condition type.. especially Pricing..
There are authority check that are embedded as Reqt and AltCTy in the IMG at the pricing procedure level for different condition type.
Could someone explain me what they are for..?
Thanks
Jac

Hi,
authority check is the std sap methodology of check the permitted authorisation values for every transaction and every user.
here in this example;authority object is used to maintain or change condition record for allowed condition types.
scenario eg;if we maintain create value for user mukund for pr00 condition type ,system allows me only for creating .if we maintain change value for user sherin for condition type,system allows to change the values.
net net i can create and u can change ,not visa-viz or any body else cannot do it.
hope this is clear.if it helps REWARD!!!!!!!

Restriction for condition type

Hi,
I want to restrict some users to do not change the basic price (PR00) in sale order (VA01/VA02), Plz let me know how I can do this.
regards,
sps.

The objects concerned have to be:
V_KOND_VEA Maintain condition: Auth. for use/appl./cond.type/table -- (Deals with condition records)
V_KONH_VKO Condition: Authorization for Sales Organizations
V_KONH_VKS Condition: Authorization for Condition Types
But in the standard system VA02 has these objects set to No check in SU24. You may have to modify this to Check/maintain and then maintain the values in the users role. Like you can have:
Object : V_KONH_VKS Condition: Authorization for Condition Types
Condition Type: PR00
Actvt : 03
Thanks & Regards
JP

To change vendor no for condition types using BAPI_PO_CHANGE

Similar Messages

Maybe you are looking for