Condition Type PBXX

Hi,
I created a PO in our production system. Following are the condition types which gets picked based on the process
1. When i create a material and a inforecord in the PO the condition type which is used in J3AP
2. When i create a material and not create an inforecord in the PO the condition type which is used is J3AX
There are instances in my PO where either of the above two condition types are not picked i get this condition type PBXX, any reason as to why this is happenning.
Thanks & Regards
Shabeen Buhary

Hi
As you mentioned
J3AP
J3AX
PBXX
these three condition are maintain in your pricing procedure
1)please check which is required condition and which is manual condition
2) while creating Po which purchasing organization you are using check this it my different for different PO
3) check you vendor master record and check which schema group you have assign in vendor master record purchasing tab
4) check access sequence also for theses condition
5) check condition record for theses condition for material ,vendor and plant combination ,you may have different combination
Regards
Kailas ugale

Similar Messages

Condition type PBXX problem

Hi
We have entered a purchase order, where the condition type PBXX is assigned a condition value even though there has been no manual entry.
The analysis of the pricing tells me the following information:
"Condition type PBXX - Message 207 - Condition has been found (without condition record)"
Is there any way we can trace where the condition type PBXX picks up the price from?
Is there anyone who has a clue on why the PBXX has been assigned a price at all?
Regards,
Lars

Hi
You can find it out
Go to condition tab > click on taxex > analysis it will shows all the condition values click on PBXX or PB00 below that you an see the condition maintained doubble click ont he same it will take you to the condition.
Regards

Condition Types PB00 & PBXX

As we know, in Purchase orders, Condition type PB00 flows from Outline agreements/inforecord/Condition records etc, while condition type PBXX is to be maintained manually.Also PBXX if maintained supersedes PB00 i.e is considesed for Gross/Net price calculations.
The requirements at a client's place is as follows:
For most of the regularly procured materials, contracts are maintained. Hence generally the P.O. price will be automatically determined as PB00. However there are cases where P.O is placed at a price which is different from generally agreed price maintained in contracts. In such cases price is to be entered manually as PBXX in P.O.,but the defaulted price should also remain i.e the p.o.should show both PB00 & PBXX so that Purchase Manager's attention is drawn to such cases
The issue is while standard Gross/Net/Tax calculations are taken care of ,subtotals in the pricing schema are going wrong. To illustrate...
Step   Counter   condition type      Description            from      To
10        1               PB00            Gross Price
10        2               PBXX            Gross Price
20        1               R000             Discount                   10       10
                                                  Subtotal (Net price)    10       20
The subtotal(Net price) which is the base for some of the further condition types in the schema , calculated as sum of PB00 & PBXX minus Discount. It should be PB00 minus discount if PBXX (manual price is not maintained) & PBXX minus discount if the same is maintained.
Will appreciate your inputs
Thanks

Dear,
The difference between pricing conditions PB00 and PBXX is :
PB00- automatic pricing - can be used for automatic pricing determination
PBXX- manual pricing - used for manual pricing.
When you maintain the pricing condition for the PO, the system will look at the available condition records (for PB00) and make the automatic pricing determination. In case, such condition records were not defined, then it is mandatory that you have to maintain manually the pricing condition where PBXX will be automatically defaulted in replacement for PB00.
Regards,
Syed Hussain.

Condition type PB00 and PBXX

Dear Gurus,
When system pick condition type PB00 and when it picks PBXX ?
I have made one scheduling agreement having 20 line items. For some line items it has picked condition type PB00 and for rest it has picked PBXX. Why system is picking PB00 for some line items and PBXX for rest ?

Hi,
If you create an Info Record manually or automatically the gross price is entered or adopted is assigned to condition type PB00.
When PO is created with reference to a contract or a quotation a vendor`s gross price for a material is adopted from the Info Record condition. (or where appropriate from PO price history) as default value for condition type PB00.
If no valid info. record condition exists and no order price history can be found, the R/3 system is not able to suggest a price and requires the manual entry of price and a manual entry of net price. The manually entered price is assigned to the condition type PBXX.
These two condition type for the gross price must be available in the calculation schema assigned to the standard PO. In the standard system these are the condition type PO00 and PBXX. An access sequence is assigned to PB00 so that the price determination process can be carried out for this condition type. No access sequence is assigned to PBXX . PB00 must come before PBXX in the calculation schema. You can also use your own comparable condition type in place of PB00 and PBXX.
At the time a PO is created, is the system finds a condition record belonging to PB00 with valid condition, PBXX is irrelevant. PBXX is taken into account only if requirement 6 is fulfilled. Requirement 6 checks the condition exclusion indicator (KOMP-KZNEP).
Hope this lengthy answer clears your doubt(s)!!
Reetesh

CONDITION TYPE AND MATERIAL

Hi,
Is there any relation between material and condition type(at item detail level) in PO?
I am making one PO, when i use material 40 (stock) condition type PB00 gets populated automaticaly and in case of material 29708 (account assignment PO), condition type PBXX gets populated. How and where this is controlled?
Regards,
Satyendra

hi,
PB00 is having the access sequence as gross price hence
when u have created inforecord,contract or scheduling aggrement the values will be copied from there only.
for PBXX u need to maitain the value manualy because it is not having the access sequence.
regards,
sujit

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

Related to condition types and access sequence

Dear all,
i want to know abt one scenario, m using a pricing procedure with my service PO: ZVSTOT, in this Procedure, 12 condition types are there, during searching i found tat 3- 4 condition are are using different different access sequence, so i want to know tat in what procedure, we do it, what is use of it.?
plz reply me.

Hi Nisha,
Prcing procedure configured in your service PO PO: ZVSTOT, Based on this pricing procedure system adopted the condition type in PO.
Please go through this below link to better understanding the MM-Pricing procedure
http://it.toolbox.com/wiki/index.php/Pricing_Determination_Process_-_MM
http://www.sap-img.com/materials/steps-for-mm-pricing-procedures.htm
CONDITIONS OR PRICING PROCEDURE or PRICE DETERMINATION PROCESS
We deal with the Pricing Procedure for vendors.
PB00 Gross Price (info record, contract, scheduled Agreement)
PBXX Gross Price (PO)
FRA1 Freight
RA00 Discount on net
RA01 Discount on Gross
ZA00 Surcharge on net
SKT0 Surcharge / discount
ZPB0 Rebates
MWVS Input Tax
MWAS Output Tax
BASB Base Amount
RM0000 Calculation Schema or Pricing Procedure
(PB00 & PBXX)
RM0002 Calculation Schema or Pricing Procedure
(PB00)
PB00 --> AB00
Copy the Standard one and create new one (ours)
RM0000 contains all the condition types
Pricing Procedure (PP)
We define the pricing procedure to define condition supplement for the material price. The condition supplement specifies the discount, surcharge, freight etc that we want a system every time to access material price condition records.
The total value of the material is calculated or based on all addition and subtraction i.e. discounts, surcharge, tax freight etc
Condition Table
It is a table, which defines the structure of condition record key.
Condition Record
It is a data record used to store conditions or condition supplements, i.e. condition like, discount, freight, and surcharge, Tax etc.
Condition Type
It is used for different functions. In Pricing the condition types leads you to differentiate different types of discounts, in output determination, batch determination, difference between two output types, such as delivery note or order confirmation, between different strategy types
Access Sequence
It specifies the order in which system searches or access the condition records from condition table
Difference between PB00 & PBXX
1. Condition maintained in PB00 is time dependent whereas PBXX is time independent.
2. Condition type PB00 u2013 used for IR, RFQ, Contract, Schedule Agreement
Condition type PBXX u2013 used for PO.
Calculation Schema
The main function of calculation schema is to provide framework of steps for the price determination process to specify the discounts, surcharge, freight rebate etc.
It also determines the sequence of conditions that are to be followed and in which sequence.
Schema Group Vendor
The main function of it is to identify or to pick the right process and conditions for a particular vendor.
Schema Group Purchasing Organization
Key that determines which calculation schema (pricing procedure) is to be used in purchasing documents assigned to the relevant purchasing organization.
Schema Group
It allows to group together the purchasing organizations, which uses the same calculation schema.
Steps: -
1. Create Access sequence
2. Create condition types
3. Create pricing procedure or calculation schema
4. Link pricing procedure & access sequence to condition type
5. Create schema group for vendor
6. Create schema group for purchase organization
7. Assign schema group vendor-to-vendor master record in purchasing data view
8. Assign schema group purchase organization to our purchase organization
9. In inforecord purchase organization data enter condition types and pricing or calculation procedure
CUSTOMIZE SETTINGS: -
SPRO > IMG>MM>PUR>Conditions -->Define price determination Process
1. Define access sequence
2. Define Condition type
3. Define cal. Schema
4. Define schema group
o Schema group vendor
o Schema group purchasing group
5. Assignment of schema group to PUR org
6. Define schema determination à determine cal schema for standard PO.
With Thanks,
Thiru

Condition type PB00 and PBXX, coming in the same PO Item

Hi,
In the PO (created with reference to Outline Agreement), condition types PB00 and PBXX are coming in the same line item.
In the PO output, the PB00 value is also showing up and PBXX value is also showing up. User entered PBXX value as 350000 dollars which is right, however system is picking 1.2 million dollar of PB00 from outline agreement which is not intended here. As a result of that the output going to Vendor is exceeding more than 1.2 million dollar instead of 350,000 dollars. I cannot change or delete any othe condition types.THis is a production problem.
Has anyone faced this problem. I appreciate your reply in advance.
Thanks,

Well, thanks Saurav and Prabhakaran, however the problem still stays.
The contract is created for services (1 lot), so the dollar amount can vary depending upon the service rendered by the consultant.
That mean user will only enter the service amount.
Saurav, system should not copy down PB00, it should come by itself when user enters the specific amount. And it comes from contract. PBXX should only appear if there is no PB00 maintained in the contract. This is not the case. The service amount is maintained in the contract. Also, I don't think that PBXX and PB00 should come in one line item together as normal system behaviour & as a normal business process too. Moreover, it is not happeniing in the other two line items - line item 20 and line item 30 are fine. The pricing analysis shows both the conditions as found - PB00 and PBXX, so I could not take any clue from analysis too.
Prabhakaran, system is only behaving incorrectly for line item 10. It is behaving as expected (good ) for other line items and other PO's. So, we cannot touch the pricing procedure as that will affect other line items.
Regards

Condition types PB00 and PBXX

Dear Experts,
1) Can anybody please explain that can we use Condition type PB00 in number of Pricing procedures. like i have three pricing procedures, local purchase, Import Purchase,
External Service Pricing procedure.
what is recommend, eiether to use same one (PB00) or maintain seperate condition type for each Pricing procedure ?
2) What is the difference between Condition type PB00 and PBXX ?
Waiting for your valuable reply
Thanks in Advance

Dear,
The difference between pricing conditions PB00 and PBXX is :
PB00- automatic pricing - can be used for automatic pricing determination
PBXX- manual pricing - used for manual pricing.
When you maintain the pricing condition for the PO, the system will look at the available condition records (for PB00) and make the automatic pricing determination. In case, such condition records were not defined, then it is mandatory that you have to maintain manually the pricing condition where PBXX will be automatically defaulted in replacement for PB00.
Regards,
Syed Hussain.

What is the difference between Condition Type PB00 and PBXX

Hallow all,
Can anybody please explain, What is the Difference between Condition type PB00 and PBXX in Materials Management Pricing?
And also please explain control or Application of both on Price determination ??
Thanks in Advance !!!!!

Hi,
PB00 condition type is used for automatic pricing in PO
PBXX condition type is used for manual pricing in PO
In Pricing access sequence play a vital role . If you need pricing automatic in the PO, you have use of Access Sequences and Schema Group of Vendor.You can see the difference in both standard condition type PB00 and PBXX, where as PB00 is assigned to Access sequence(0002)but in case of PBXX no access sequense assigned.
Regards,
Biju K

PBXX and PB00 Condition Type determination

Hi all,
Related to this Purchase condition type, i would like to know whether it is possible to have further determination.
Example, the condition type for PB00 is based on vendor/material/purg org/ plant to determine that PB00 has been selected.
Currently i have a scenario whereby user has will ensure the existing of PBXX are based on vendor/material/material group/purg org/plant to determine the PBXX.
Is there anyway we can include any of this selection to make it more selective.
Hope to hear fromyou.

Hi Yeong,
I understood your requirment that you want PBXX to condition record based and want it to be automatic determined by system rather then putting it manually in PO based on vendor/material/material group/purg org/plant. So answer to your question is "Yes" you can do it. Follow the following
1) Create a New Condition Table
2) Create a new access sequence
3) Assigned to PBXX
4) Then samll setting changes in PBXX
5) PBXX must be assigned in your Pricing Procedure after or before PB00 (as PB00 & PBXX by default avaliable in Standard Pricing Procedure, so it can be assumed that PB00 is already in your pricing procedure, all you need to add PBXX in Pricing Procedure )in order to picked automatically in PO (So insure PBXX is in you pricing procedure)
4) Maintain the condtion record based on vendor/material/material group/purg org/plant and then system will automatic determine the value...
So lets start creating for you...
1)Create a New Condition Table
TC - M/03 (Create Condition Table)
Enter your Table No Say - 901, Press Enter, there is two seperate Column fields One is Selected fields (its rows must be blank as we are going to create a new condition table), Seconf one is Field Catlog (All possible Value what you want to be in your access sequence)
So in this case you fields are Vendor, Material. Material Group, Purg Org, Plant. So find these fields one by one in Field Catlog and double Click over it then you will noticed that it (Say Vendor field) is also coming in Selected Fields column. So logic is to put all fields (Vendor, Material. Material Group, Purg Org, Plant) to be in Selected fields column. (Hint if you not found any field in Field catlog then you page up and page down key). So I can assume up to know that you put all fields (Vendor, Material. Material Group, Purg Org, Plant) in Selected Fields Column now save. So now creation of New Condition Table is over.
Continue in next message.....
<h5>Note: Please assign valuable point in order to encourage contributors for helpful answers to your queries...</h5>
Best Regards,
Silky

Difference between PB00 and PBXX condition types?

Hi All,
Can you please tell me the difference between a PB00 and a PBXX condition type and their significance as to which is used when?
Regards,
V S

Hi,
PB00 - Maintained through condition records in turn through access sequence gets fetched ( ie through Info record ) also this is a time dependent condition.
PBXX - This particular condition is maintained whenver the rate of the material in the PO is to be maintained manually as there no condition records exists for this. This condition is free from access sequence also it does not possess any validity thereby we can call this condition type as a time independent condition.
Regards,

Creation of new condition type: MWST

Hi, Everyone.
I would like to ask for some help regarding this issue: Creation of new condition type: MWST with the following details:
1. For the country French Polynesia, Create a new VAT condition of 10%.
2. Create a new one called : Class : Z u2013 Designation : France : TOM corresponding to 10 % of VAT to be invoiced
and then associate this new VAT code u201CZu201D to the applicant Nr 221860
If you could provide me a step by step process on how to resolve this, it would be very much appreciated. Thank you so much.

Hello
What type of condition type you want.
It is always advisable to create a new conditon type copying a standard condition type.
For gross price condition types select PB00/PBXX
For freight charges, Copy FRA1/FRB1
Regards

Condition Types in Scheduling Agreement(Urgent)

Dear Experts.
This is a query with reference to my earlier issue Changes in Condition ME32L.As per suggestions, to get validity periods i have clicked on Time dependent Condition In SPRO settings Under Define document Types.
After that i am not able to enter Custom Conditions while creating a Scheduling Agreement.So i tried by removing this Time dependent setting,then was able to enter Custom Conditions...
But i need to see validity periods too when i change condition types through ME32L...
So,Please give me appropriate Suggestion....
Thanks and Regards
MK

I'm not sure about your own pric proc, but in standard it should works, and also its apply per organization level.
RM0000 and RM1000
    Control the price determination process in POs, quotations, and
    scheduling agreements.
    Both calculation schemas require 2 condition types for the gross
    price: one for automatic price determination (standard: PB00) and
    one for manual maintenance (standard: PBXX).
RM0001 and RM1001
    Determine which condition types you can enter in purchasing document
    headers with time-dependent conditions (e.g. contracts).

PO BAPI Problem in condition types

Hi,
I am facing a strange problem in creation of PO through "BAPI_PO_CREATE1".
In the Item condition internal table, I am passing the condition types.
The PO is getting created successfully.
Eg. I pass conditions and their values as follows:
PB00 : 1000
ZB00 : 1000
FRB1 : 1000
The PO is created successfully and we can check the prices updated properly.
Now,
When I create a second PO with the same values, the prices are taken from the last PO and the prices from
my code(which are passed through BAPI) are added to the last value.
If I run the program with the same values as above, the PO is created with the values 2000.
Third time it is 3000 and so.
The value from the last PO is coming into the new PO.
Please advise me if anything missing.
My code is below::
================
*& Report ZTEST_PO
REPORT ZTEST_PO.
data : HEADER like BAPIMEPOHEADER .
data : HEADERX like BAPIMEPOHEADERX .
data : POITEM like BAPIMEPOITEM occurs 0 with header line.
data : POITEMX like BAPIMEPOITEMX occurs 0 with header line.
data : POSCHEDULE like BAPIMEPOSCHEDULE occurs 0 with header line.
data : POSCHEDULEX like BAPIMEPOSCHEDULX occurs 0 with header line.
DATA : RET LIKE BAPIRET2 OCCURS 0 WITH HEADER LINE.
DATA : ret1 like bapiret2.
Data PO like BAPIMEPOHEADER-PO_NUMBER.
data : pocond like BAPIMEPOCOND occurs 0 with header line.
data : pocondx like BAPIMEPOCONDX occurs 0 with header line.
*pocond-CONDITION_NO = '00000'.
pocond-itm_number = '000010'.
pocond-COND_ST_NO = '001'                                   .
*pocond-COND_COUNT = '1'.
pocond-COND_TYPE = 'PB00'.
pocond-COND_value = '500'.
pocond-CURRENCY = 'EUR'.
pocond-CURRENCY_ISO = 'EUR'.
pocond-CHANGE_ID = 'I'.
APPEND POCOND.
**pocond-CONDITION_NO = '00000'.
*pocond-itm_number = '000010'.
*pocond-COND_ST_NO = '10'                                   .
*pocond-COND_COUNT = '2'.
*pocond-COND_TYPE = 'PBXX'.
*pocond-COND_value = '555'.
*pocond-CURRENCY = 'EUR'.
*pocond-CURRENCY_ISO = 'EUR'.
*pocond-CHANGE_ID = 'U'.
*APPEND POCOND.
**pocond-CONDITION_NO = '00000'.
*pocond-itm_number = '000010'.
*pocond-COND_ST_NO = '20'                                   .
*pocond-COND_COUNT = 0.
*pocond-COND_TYPE = 'ZB00'.
*pocond-COND_value = '666'.
*pocond-CURRENCY = 'EUR'.
*pocond-CHANGE_ID = 'U'.
*APPEND POCOND.
**pocond-CONDITION_NO = '00000'.
*pocond-itm_number = '000010'.
*pocond-COND_ST_NO = '30'                                   .
*pocond-COND_COUNT = 0.
*pocond-COND_TYPE = 'FRB1'.
*pocond-COND_value = '777'.
*pocond-CURRENCY = 'EUR'.
*pocond-CHANGE_ID = 'U'.
*APPEND POCOND.
*pocondx-CONDITION_NO = '00000'.
POCONDX-ITM_NUMBER = '000010'.
POCONDX-COND_ST_NO = '000'.
*POCONDX-CONDITION_NOX = 'X'.
*POCONDX-COND_ST_NOX = 'X'.
POCONDX-ITM_NUMBERX = 'X'.
*POCONDX-COND_COUNT = 'X'.
POCONDX-COND_TYPE = 'X'.
POCONDX-COND_value = 'X'.
pocondX-CURRENCY = 'X'.
*pocondX-CURRENCY_ISO = 'X'.
pocondX-CHANGE_ID = 'X'.
APPEND POCONDX.
HEADER-COMP_CODE = 'TF01'.
HEADER-DOC_TYPE = 'DMPO'.
HEADER-VENDOR = '0000000317'.
HEADER-LANGU = 'EN'.
HEADER-PURCH_ORG = '1001'.
HEADER-PUR_GROUP = '110'.
HEADER-CURRENCY = 'EUR'.
HEADER-DOC_DATE = '22.10.2007'.
HEADER-REF_1 = '999999999999'.
HEADERX-VENDOR = 'X'.
HEADERX-PURCH_ORG = 'X'.
HEADERX-PUR_GROUP = 'X'.
HEADERX-REF_1 = 'X'.
POITEM-PO_ITEM = '00010'.
POITEM-MATERIAL = '00042199730L'.
POITEM-PLANT = '1000'.
POITEM-STGE_LOC = '1030'.
POITEM-MATL_GROUP = '01'.
POITEM-QUANTITY = '10'.
POITEM-PRICE_UNIT = 500.
poitem-calctype = 'C'.
append POITEM.
POITEMX-PO_ITEM = '00010'.
POITEMX-MATERIAL = 'X'.
POITEMX-PLANT = 'X'.
POITEMX-QUANTITY = 'X'.
POITEMX-PRICE_UNIT = 'X'.
append POITEMX.
POSCHEDULE-PO_ITEM = '00010'.
POSCHEDULE-DELIVERY_DATE = '30.10.2007'.
append POSCHEDULE.
POSCHEDULEX-PO_ITEM = '00010'.
POSCHEDULEX-PO_ITEMX = 'X'.
POSCHEDULEX-DELIVERY_DATE = 'X'.
append POSCHEDULEX.
CALL FUNCTION 'BAPI_PO_CREATE1'
EXPORTING
    poheader                     = HEADER
    POHEADERX                    = HEADERX
POADDRVENDOR                 =
TESTRUN                      =
MEMORY_UNCOMPLETE            =
MEMORY_COMPLETE              =
POEXPIMPHEADER               =
POEXPIMPHEADERX              =
VERSIONS                     =
NO_MESSAGING                 =
NO_MESSAGE_REQ               =
NO_AUTHORITY                 =
NO_PRICE_FROM_PO             =
IMPORTING
   EXPPURCHASEORDER             = PO
EXPHEADER                    =
EXPPOEXPIMPHEADER            =
TABLES
   RETURN                       = RET
   POITEM                       = POITEM
   POITEMX                      = POITEMX
POADDRDELIVERY               =
   POSCHEDULE                   = POSCHEDULE
   POSCHEDULEX                  = POSCHEDULEX
POACCOUNT                    =
POACCOUNTPROFITSEGMENT       =
POACCOUNTX                   =
   POCONDHEADER                 = POCOND
   POCONDHEADERX                = POCONDX
    POCOND                       = POCOND
    POCONDX                      = POCONDX
POLIMITS                     =
POCONTRACTLIMITS             =
POSERVICES                   =
POSRVACCESSVALUES            =
POSERVICESTEXT               =
EXTENSIONIN                  =
EXTENSIONOUT                 =
POEXPIMPITEM                 =
POEXPIMPITEMX                =
POTEXTHEADER                 =
POTEXTITEM                   =
ALLVERSIONS                  =
POPARTNER                    =
POCOMPONENTS                 =
POCOMPONENTSX                =
POSHIPPING                   =
POSHIPPINGX                  =
POSHIPPINGEXP                =
NFMETALLITMS                 =
if RET-type NE 'E'.
      CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
        EXPORTING
          WAIT   = 'X'
        IMPORTING
          RETURN = ret1.
write : ' PO Created : ', PO   .
    ELSE.
      CALL FUNCTION 'BAPI_TRANSACTION_ROLLBACK'
        IMPORTING
          RETURN = ret1.
    ENDIF.
================

Any input??

Condition Type PBXX

Similar Messages

Maybe you are looking for