Condition types from SRM to backend

Hi All,
When accepted bid (complex prices with condition types) is converted to PO, in backend PO is created with net price only. Is there a way to move the condition types also to backend. Can we use any Badi in this case?
Thanks in advance.
Will reward full points for the reply.
Venu

Hi
<b>Either you need to maintain the Condition types locally in SRM system by maintaining Z tables and then create your own logic for pricing in SRM. I guess, this will be much more complex activity.</b>
<u>I know there is some issues, but, Anyways, you have to go for this approach.
You need to go for custom fields and then get the data passed back over to R/3 PO using any of the BADIs
BBP_CREATE_PO_BACK / BBP_TARGET_OBJECTS / BBP_TARGET_OBJTYPE / BBP_CREATE_PO_NEW
in SE18 Transaction.
Refer OSS note - 672960 and 485891 for creating customer fields.</u>
Also, incase this don't suits your requiremnents, Please raise an OSS message with SAP.
Regards
- Atul

Similar Messages

Condition types from SRM system t backened system

Hi,
We are using SRM 7.0, we have decided to go ahead with the pricing proceedure and the condition types which are there in ECC the same should be replicated to SRM.
We have created the same pricing proceedure and the calculation scheema in SRM.
Now my requirement is when i create a PO with the conditions and when i am transfering to ECC the PO should also be with the condition types. It should be a similar PO in ECC.
Is this can be addressed.

Hi
I wish to update on this further:
Under Copying rules for Conditions, for Source table 350 (Sales Organization), I am maintaining report "RV15CC03" which is material to material.
I think I need to use something different since I am copying data from Sales Org to Sales Org.
I don't find a suitable program for Sales Org here.
Any ideas on how to go about.
Thanks
Satya

Pricing condition types in SRM 7.0

Hi,
We are using SRM 7.0, we have decided to go ahead with the pricing proceedure and the condition types which are there in ECC the same should be replicated to SRM.
We have created the same pricing proceedure and the calculation scheema in SRM.
Now my requirement is when i create a PO with the conditions and when i am transfering to ECC the PO should also be with the condition types. It should be a similar PO in ECC.
Is this can be addressed.

Hello All,
As I have already mentioned the condition types in SRM are identically matched to ERP condition type hence the data is flowing correctly and even the idoc has the z-condition type Z123.The IDOC in backend ERP has status 53.
On trial and error method we did unchecked the manual indicator check in the pricing schema for the relevant condition type and because of that now the Z-condiiton type can be seen in the backend ERP contract.
If the indicator was checked, this means that this condition can be maintained only manually (directly in the transaction
ME32K in ECC) and nothing can be transfer from other source.
Note: If the same condition type is being used in more than one pricing procedure then ensure that the check bok is unchecked for agianst the relevant condition type.
Thanks,
Yatin

Creating new pricing condition type in srm ecs

Hi Guru's
I see that there is an option to select the Source system " local" , "other system, eg: R/3" while creating a new condition type in SRM. can you please let me know what is the importance of this? can we determine price in srm using backend pricing conditions? can we invoke the backend pricing procedure from srm and populate the price in SRM PO?
any helpful info would be appreciated
regards
deepu

Hi Nitin,
Appreciate your response. Can you please let me know how major development is it? if you can provide highlights that would be helpful. I do understand that we can customize the pricing procedure in SRM. Can you please share if you have any documentation regarding creating new condition types, access sequences, condition records in SRM similar to ECC? it would be appreciated if you can send it to pradeepwsu(gmail) id.
Thanks in advance
Deepu

Condition types from Central Contract not copied into Purchase Order

Hi,
When creating a central contract from SRM to ECC, all the condition types are copied well.
But when creating a shopping cart from SRM or a PO in ECC referencing the created central contract, the condtion types are not displayed in the conditions tab. (Only Condtion type PB00 is displayed.).
What can I do to assure, that all the condition types from the contract are displayed in the PO.
Do I have to do some customizing, or is there a SAP Notes to resolve this.
Regards,
Alexander

Dear Poster,
As no response has been provided to the thread in some time I must assume the issue is resolved, if the question is still valid please create a new thread rephrasing the query and providing as much data as possible to promote response from the community.
Best Regards,
SDN SRM Moderation Team

Mapping of invoice document type in SRM and Backend

hi,
I need to map invoice document type in SRM and backend. We are in SRM5.0.
e.g. when we create no PO invoice , we need to select document type from drop down and that document type should be replicated to backend invoice document type.
1. There is no list in drop down of invoice document type ( RE/RN)
2. How it will be replicated to back end document type when enter document type instead of selection?
If anyone came across this, pls let me know.
regards,
Rahul Mandale

Dear Poster,
As no response has been provided to the thread in some time I must assume the issue is resolved, if the question is still valid please create a new thread rephrasing the query and providing as much data as possible to promote response from the community.
Best Regards,
SDN SRM Moderation Team

Restrict referance of pricing and condition type from latest PO.

Hi Experts,
I am creating Purchase order and at the time of creation of purchase order system is copying prices and condition types from latest PO.
Which is not desirable to our business process, when I dig out I found out that in standard SAP system
The system looks at pricing in the hierarchy order as below:
u2022     Contracts/scheduling agreement
u2022     Condition records
u2022     Info Records
u2022     Last purchase document
So can some one help me with information how to restrict system to follow this referance of pricing.
I want to enter price as well as condition type manualy every time user create a purchasing document.
Also i want to know can it be restricted specificaly for few document type.
Thanks
Best Regards
Ritesh

Hi sir
can we try this
Use the user parameter EVO to indicate that no price adoption from last Purchase Order must take place:
IMG: MM -> Purchasing -> Environment data -> Default values for Buyers
-> Setting for Default values.
Select or setup a default value and on the "price adoption" tab you may choose how copying of conditions from last purchase order must behave. Select "Do not copy".
Then assign this default value to the user, using the EVO parameter.
[http://sap.ittoolbox.com/groups/technical-functional/sap-log-mm/price-to-flow-from-info-record-at-plant-level-813066]
[Re: new info record with same details as archive one.;
check following notes it may helfull
569885 About Info Record Update indicator (EKPO-SPINF)
13127 Update in info record from PO, quotation, contract
430543 FAQ: Purchasing info record
675523
456691
Regards
Kailas ugale

Flowing of the Condition type from Sales Order to invoice

Dear All,
I'm facing a problme in the copying the condition types from Sales order to Invoice.
The details are as mentioed below:
I have a Condition type CONC and made the Copy of the Condition typs as ZDIS.So that CONC's value will be debited and ZDIS' value will be credited in the FI..
But ALL the condition types which i have mentioed including tax and discounts condition types are copying from Sales order to invoice.Except CONC.
I have checked all the copy controls,i'm sure those are OK.Bcoz other condition types are working perfectly fine.
What could be the reason for this???
Will be any setting for on condition type level for copy controls???
Please Guide me its URGENT.
Thanks
Vinay

hi
from which condition type u have copied this CONC , can u pl elaborate more on this.
and just write what is exact scenario and whats going wrong?
in copy controls check for pricing source and pricing type.
regards
mandar

Condition types in SRM for mapping purposes with backend contracts

Hello,
We need to map condition types for the creation of a Backend contract on the basis of a accepted bid.
We use SRM 5.0 but our products do not have prices in their product master!
We use the catalog funcion to indicate the prices of the materials. for service-items we manually add the prices in the Shopping cart.
How can I find out what conditions types we use in these circumstances in SRM 5.0?
What condition type are we using in the case of materials?
What condition type are we using in the case of service-items?
Thanks for any reply.
Aart

Hi
You can map the condition type 01CT (gross price) in SRM with PB00 for Gross Price in contracts. Standard SRM generally work with simple pricing with gross price condition types and do not have complex conditions unless you customize it. For material or services, it should matter from condition perspective unless you have done some specific customization.
Regards,
Sanjeev

The Po condition transfered from SRM to ECC

Dear ,My Experts :
   I work in SRM7.0 .Extended Classic Scenario .
   I create PO with PO condirtion in SRM system .The PO will be transfered to ECC system . But the condition is not transfered .
   So ,i want to know why ,and how to do ?
   Best Regards!
   Alex!

Hello,
As the price determination has already done by IPC for the leading SRM PO, in standard when a PO is transfered to the backend, only the netprice is passed to backend and no further price calculation will be done at the backend. The backend PO takes what ever price SRM sends and creates the PO at the backend with a base condition type PBXX. To intimate the backend not to perform any further price calculations, SRM transfers PO_PRICE = 2. So that backend reads this value and takes only the SRM PO price and no pricing conditions are passed to the backend PO.
This is the standard design of extended classic scenario.
There are not consulting notes for transfering pricing conditions to the backend in ECS. If you want to use the backend conditions you have to implement the BADI BBP_ECS_PO_OUT_BADI to override the value of PO_PRICE = 2.
I hope this helps.
Kind regards,
Ricardo

New created condition types from CRM to R3

I have do initial download with DNL_CUST_CNDALL. The condition customizing(pricing procedure, condition type, condition table...) have been downloaded from R3 to CRM.
In transaction R3AC4(Delta download) two entries for CONDCUSTOMIZING and CONDITIONS exist for delta download of condition customizing and record from R3 to CRM.
But when I created a newe condition type in R3, it is not automatically transfered to CRM. I also tried use transaction R3AR4 (request) to synchronize object DNL_CUST_CNDALL. But the new created condition type is still not availabe in CRM.
Could anyone give some help?
Regards,
Hui Wang

I have restart the DNL_CUST_CNDALL, the new created condition type are transfered to CRM. But when I create another new condition type again in R3, it is not transfered.
Any other advice?
Thanks!
> Hi,
>
> Do the initial load of DNL_CUST_CNDALL once again.
> This should help.
>
> Best regards,
> Vikash.

ME21N : Donu2019t copy the price for all condition types from last po

Dear.
When I create a purchase order the price for all condition types are copied from last purchase order inside the info-record.
But I have some condition types like FRA1 or FRA2 that I donu2019t want that system transfer price from last purchase order.
How can I do that ?
Thanks.

Hi Cris,
Go to SPRO>MM>PUR>Info Record>Define Price History> Here with your Purchasing organization if the tick is active that
Specifies that the order price history (PO price history) is to be updated with the effective price.
Normally, the order price history is updated with the net price.
Procedure
Set this indicator if you want the order price history to be updated with the effective price.
Thanks
Diwakar

PO release/distribution (from SRM to backend) FModules?

Hi experts,
I need to create a report that allows the user to release/distribute (sorry if these are not the right words to call the process) a PO ... My report actually retrieves the header of the purchase order ,that has status "waiting" ("park") in SRM (a change version)... so, given the header, is there a FM to release easily the po ?
(excuse the terminology, I'm not sure that's correct: I talk about release/distribute a PO meaning the process that brings a correct po from SRM to the backend).

Hi sanjeev, tried your solution without success. I get an error message, BBP_PD381.... I call the FM in this way:
CALL FUNCTION 'BBP_PD_PO_STATUS_CHANGE_WF'
EXPORTING
iv_guid = srm_change_header_guid
iv_status = 1
where srm_change_header_guid is the header's guid of the change version on my PO, the one I'd like to release.
Some infos from debugging.... the error comes from the call function that follows:
CALL FUNCTION 'CRM_STATUS_CHANGE_FOR_ACTIVITY'
(source report: LBBP_PDF0Y)
values of the parameters in debug are:
check_only = X;
client = sy-mandt;
objnr = p_new_guid (which is the guid of the header of the change version)
vrgng = 'RELP'
XNOAUTO = 'X'.
The message is hard to translate in english, anyway says something like "error on modify state RELP. "Release purchase order not allowed".
Any hint?
Thanks in advance.

Identify TAX condition type from pricing procedure

Hello,
I need to identify Tax condition type for various countries used in Old sales orders.We are moving to an external Tax engine and I need to identify what condition are being used to calculate tax in various countries. I know the pricing procedure but we have a lot of sales order and there is no documentation available.Is there any table where I can filter based on the sales org from existing sales order and find the Corresponding Tax condition type.
Regards,
Amanda

One option is
you have to execute SE16, input table KONV where you maintain the tax condition type and execute.
System will populate all SD documents that are having that tax condition type. There you have to copy the field "Doc. condition" and paste it in VBAK table in SE16 so that you will get all sale orders.
The other option is
you need to identify what access sequence is maintained for that tax condition type which you can see in V/06. Next go to V/07, select this access sequence and execute. There check what tables are maintained. For example, in your case, it could be table 110. So you have to develop a query by table joining A110 and VBAK in SQVI where you can take sale orders based on sales organisation.
thanks
G. Lakshmipathi

Change decimal points in SD Condition type from 2 to 3, for EU

Hello,
We have a slight problem with the amounts. We are using resource related billing in the project and to track some expenses, there are some condition types created. Since the currency is maintained as EU, the decimal places are maintained as 2 decimals in OY04 and we dont want to change that.
We face an issue, when SAP Converts condition value from 3 to 2 decimals
For example, when in Contract we have an Condition Value of 100.025, this is converted to 100.03 and tax is applied on this amount.
When we create an invoice and subsequently a Credit Memo request, that will contain more than one item, and the sum of all items will have to sum up to 100.03, but this is never the case, as with the application of tax rate, the value comes to something like 100.02 or 100.04..
With 3 decimal points, this amount adds upto correct value.
So our ideal solution will be the have the Condition Values as 3 decimals and the Net value in 2 decimals.
Is there something that can be done for this?
Hoping for a quick response.
Regards
Maddy

SAP stores the 3 decimal value in XKOMV-kbetr and Xkomv-kwert is calculated based on this 3 decimal values...
I had a similar scenario with currency conversion and rounding issue in sales Order and Invoice processing, in VOFM routines... so I used a Floating point value and converted to character value and then used that 3 decimal value for calculation.

Condition types from SRM to backend

Similar Messages

Maybe you are looking for