Transfer PO Conditions to R/3 in Extended Scenario (SRM 5.0)

Hi all,
We are using SRM 5.0 Extended Scenario.
For controlling reasons we would like to transfer the whole conditions scheme (PO) from SRM to R/3 as well, so you could see the price calculation with rebates etc. in the R/3 position as well.
I have done some steps based on forum suggestions but still i have some doubts.
1. I have implemented the badi BBP_DRIVER_DETERMINE.
2. I have copied the function module B46B_DPO_TRANSFER into
ZB46B_DPO_TRANSFER
3. In that ZB46B_DPO_TRANSFER function module I have added the following
coding also.
DATA: BEGIN OF wa_pocondheader.
INCLUDE STRUCTURE bbp_bapimepocond.
DATA: change_id TYPE c,
END OF wa_pocondheader.
DATA: lt_bapi_pocondheader LIKE TABLE OF wa_pocondheader.
DATA: wa_bapi_pocond LIKE wa_pocondheader.
DATA: lt_bapi_pocond LIKE TABLE OF wa_bapi_pocond.
4. I have modified the following code in my ZB46B_DPO_TRANSFER
function module
CALL FUNCTION 'BBP_PO_INBOUND' DESTINATION lv_destination
EXPORTING
poheader = ls_bapi_poheader
poaddrvendor = ls_bapi_poaddrvendor
no_messaging = c_on
poheader_ext = ls_bapi_poheader_ext
IMPORTING
expheader = es_expheader
TABLES
return = lt_bapi_return
poitem = lt_bapi_poitem
poaddrdelivery = lt_bapi_poaddrdelivery
poschedule = lt_bapi_poschedule
poaccount = lt_bapi_poaccount
polimits = lt_bapi_polimits
poservices = lt_bapi_poservices
posrvaccessvalues = lt_bapi_posrvaccessvalues
poservicestext = lt_bapi_poservices_text
potextheader = lt_bapi_poheader_text
potextitem = lt_bapi_poitem_text
poitem_ext = lt_bapi_poitem_ext
popartner = lt_bapi_popartner
customer_fields = lt_bapi_customer_fields
pocondheader = lt_bapi_pocondheader
pocond = lt_bapi_pocond
EXCEPTIONS
communication_failure = 1 MESSAGE lv_msg_text
system_failure = 2 MESSAGE lv_msg_text
OTHERS = 3.
I need some advise how to fill in my SRM conditions correctly into the new table (lt_bapi_pocondheader, lt_bapi_pocond) in my ZB46B_DPO_TRANSFER function module so that R/3 is able to generate the conditions within my PO positions.
So Please suggest how to do this.
Note: If anybody is having code for this please share that will be very helpful for me.
Thanks and Regards,
Natchiappan.M

Hi Natchiappan.M,
Have you found any solution of how to read condition types and fill.
Actually i have the same requirement so please let me know if you found some solution for the same.
Thanks in advance.
Regards,
Hemant

Similar Messages

Error while transfering PO in extended Scenario -- error 06 053 in R/3

Hi,
while transfering a PO from SRM to R/3 in extended Scenario we get an error in RZ20(SRM):
"No selectable items exist for purchase requisition xxx" --> error number 06 053
Whats happening here?
The PR is released in R/3 and yet not transfered into another PO.
Material and Material Group are the same, there is no contract involved and no differences within PO to PR.
Any ideas how to solve this problem?
Thanks and best regards
Andreas

Hi muthu,
thanks, that seems not to be the problem.
By using the fbgendat report in backend I found out, that R/3 seems to interprete my SRM PO as a local PO?!
Might there be a problem in SRM when calling the function module BBP_PO_BAPI_STATE within method set_po_bapi_state_in_be (class CL_BBP_BS_ADAPTER_PO_CRT)?
Seems R/3 does not interprete my PO out of SRM as a SRM PO?
Does the RFC User needs additional roles for setting the BAPI_PO_STATE in R/3? (the RFC User does not have sap_all in R/3!)
Best regards
Andreas

Extended Scenario: which BE Purch Org & Purch Group ? :-(

Hi guys,
Im using SRM 4.0 sp7 (Extended Scenario), Ill have several companies in my Org. structure.. but, I have a question:
Right now, all my PO documents have just one BE Purch Org and Puch Grp. Obviously, I need to change this according to every Company Code.
Is this possible ? Is this an error in my config ? Or, Is this the extended scenario standard behavior ?
Thanks for your help !!!! =)
REgards,
Diego

Diego
It seems you have created only one purch org and assigned to one company code. that may be the reason why all PO documents refer to that company code.
Create a Purch org and Purch group for each company code with corresponding backend assignment. Then for each purch group enter the responsible organization unit and product categories in the Responsibility tab. Then check if correct company code and purch grp is picking in the PO document.
Hope it should solve your issue.
Reward points to the helpful answer.
Thanks
Jagdish

Shipment cost transfer to condition types of PO

HI! I saw this note 427944 which states the rules to transferring the shipment costs into the condition types of the PO:
The shipment cost value (without tax amounts) is cumulated for all relevant shipment cost documents for each service agent and transferred to a corresponding condition type of the purchase order item. Before cumulation, the amounts are first converted into the purchase order currency.
1. A transfer of the values for each condition type (similar to the transfer from a shipment cost document to the SD billing document) is not supported.
2. If different service agents exist in the shipment cost documents, a corresponding number of condition lines (with value 0) must be specified in the purchase order item. These can always belong to the same condition type (in schema 'Manual') or also to different condition types (not 'Manual'):
a) Manual condition lines: If the condition type in the schema of the purchase order is marked is 'manual', the condition type must be created (with value 0) in the purchase order item before the goods
receipt. If delivery costs are expected from different service agents, several non-valuated entries must be generated for this condition type. If more condition lines exist than required, these are then no longer taken into account. If condition lines are missing, the last service agents are not settled.
- Advantage: You only have to define one condition type for the delivery costs.
- Disadvantage: Each purchase order must be processed manually before the goods receipt.
b) Automatic condition lines: If the condition lines are to be generated automatically for the delivery costs (the condition type is not flagged as 'Manual' in the schema), the schema must have
enough condition types to settle several service agents. If more condition lines exist than required, these are then no longer taken into account. If condition lines are missing, the last service
agents are not settled.
- Advantage: The goods receipt can be carried out without manual preparation beforehand in the purchase order.
- Disadvantage: You must define identical condition types with different names.
I can understand point a about the manual condition lines and have tried it out myself.
But I don't quite understand point b about the automatic condition lines and so I need some clarification here.
1. Does that mean I do not need to maintain the condition type in the PO?
2. Does that mean the system will automatically find a condition to put the shipment cost for each service agent?
3. How does the system know which condition to take then?
4. I tested with the 'manual' field not flagged in the PO schema but no shipment cost is transferred. Is it because of the existence of other normal condition types that are also not manual?
Appreciate any help to this.
Thanks!
SF

No answer

Transfer of condition records

hi guys,
I have couple of questions regardign the transfer of the conidtiopn records from R/3 to CRM
IF we trying to create a new condition table ex A922 in R/3 do we need to create a new adpater object ZDNL_COND_A922 or we can download using the adpater object DNL_CUST_CNDALL.
All the condition types i mean Zxx which are created in R/3 how are they transferred to CRM .Are they transferred using the adapter object or they need to be created manaully in CRM system
Thanks in Advance
Regards,
Krishna

Hi,
Every condition customising including conditioin types and condition tables are downloaded into CRM from R/3 using Adapter object DNL_CUST_CNDALL.
But, the condition tables downloaded like this will be empty. This means they wont haev any condition record.
In order to bring condition records too, you need to create an Adapter object.
If the condition table is a standard condition table (say A340), then a standard Adapter object exists with name DNL_COND_A340.
If its a manually created condition table say A922, then you have to create an adapter object ZDNL_COND_A922. This can be created by copying any standard ada[pter object adn modify it accordingly...
Now jsut download this adapter object and it will bring all your condition records for the condition table.
Kindly reward with points in case helpful.....
Sharif

Transfer pricing conditions ( Ecc) to Customs Duty Types (GTS)

Hi Experts,
We are currently using ECC 6.0 with GTS 7.0.
In GTS 7.0 , the option to Map the Customs Duty type to Pricing condition type does not appear. Can you share where I can look for the same
The condition records from proforma Invoice (ECC) are transferred to GTS Customs Declaration.
However, we have certain condition types with calculation type as percentage in ECC which need to flow over to GTS.
1. What changes need to be carried in the corresponding boldcustoms duty type configurationbold in GTS to ensure that we get a correct data transfer..
2. what unit type / currency needs to be maintained to map the "%" appearing in condition record value (ECC) to the customs duty value (GTS).
Regards
Jasmit

Thank you Sathya,
I attempted to navigate via the given path but could not locate the option of having the assignments there.
The condition type that is in scope of the dicussion is already getting transferrred to GTS via the standard mechanism( we havent modified the BAdI for this)
However, the issue being encountered is that te condition record value holds a percentage figure.. this in turn is not getting mapped to the currency of customs duty type .
How do I achieve this mapping in GTS ... Do i need to modify the BAdi to carry out the calculation before transferring this to GTS or alternatively some standard configuration in GTS can help me achieve this mapping.
Regards
Jasmit

PO text transfer to Back-end in case of Extended Classic Scenario in SRM 4.

Dear experts,
My system is in SRM 4.0 in Extended Classic Scenario. We use in the PO internal note text and vendor But thses texts are not transfered to Back-end.
Is it normal?
Do I need to customize something?
Can it be achieved by BADi? How then?
OR is it only possible from SRM 5.0?
Thanks in advance
RD

Yes you can do this. Implement BADI BBP_CREATE_BE_PO_NEW, Refer parameter IS_SC_DOCUMENT>LONGTEXT, and CS_PO_DOCUMENT>IT_PO_ITEM_TEXT. Map the exact text-id of the R/3.
Note: if this BADI is not present, use BBP_CREATE_PO_BACK
Regards, IA

Custom Pricing Conditions not working for a PO in SRM

Hi Experts,
We are on SRM 5.0, ECC 6.0 , Extended Classic Scenario.
We configured the pricing conditions in SRM . We defined the our custom pricing condition types as below
Condition type      --- Condition Class       --- Calculation Type
Frieght(%)            ---       Prices                ---      Percentage
Frieght Value       ---        Prices                --- Fixed Amount
We also defined the Calculation Schema.
But when we try to define the pricing conditions in SRM during PO creation\change , the standard pricing condition types work but when we input the above defined custom pricing condition type, the value entered gets cleared. Pricing Overview is not calculating the values of the custom Pricing condition types.
Please assist as where i have gone wrong. Do I need to run any standard report for pricing or do i have to implement any BADI.
Thanks,
Addy.

Hi Sanjeev,
I have run SM52 and VMC is active with 4 VM's .
Please suggest.
Thanks,
Addy.
Edited by: Addy1209 on Nov 18, 2010 4:28 PM

UNCAUGHT_EXCEPTION while creating Purchase Order in Extended classic SRM 7

Hi Experts,
I am getting the following message while creating Manual or SC/PO in Extended classic Scenario (SRM7.0 with ECC 6.0)
Pl suggest what could be the problems.
Error application is coming up.
20091130
E2001
172331
wicomp03
http://wicomp03.wipro.com:8003/sap/bc/webdynpro/sapsrm/wda_l_fpm_oif/
UNCAUGHT_EXCEPTION
An exception has occurred in the procurement document methods
Form: DETERMINE_MATNR of program SAPLBBP_BD_DRIVER_46A
Form: FILL_BAPI_POITEM of program SAPLBBP_BD_DRIVER_46A
Form: MAP_BBP_DPO_TO_BAPI of program SAPLBBP_BD_DRIVER_46A
Function: BBP_DPO_TO_BAPI_MAP of program SAPLBBP_BD_DRIVER_46A
Method: IF_EX_BBP_DOC_CHECK_ICC~BBP_DOC_CHECK of program /SAPPSSRM/CL_PO_TOLERANCE=====CP
Form: DOC_CHECK_BADI_CALL of program SAPLBBP_PD
Form: PROCDOC_CROSS_CHECKS of program SAPLBBP_PD
Form: PROCDOC_UPDATE of program SAPLBBP_PD
Function: BBP_PROCDOC_UPDATE of program SAPLBBP_PD
Method: /SAPSRM/IF_PDO_BASE~SAVE of program /SAPSRM/CL_PDO_BO_PO==========CP
http://wicomp03.wipro.com:8003/sap/bc/webdynpro/sapsrm/wda_l_fpm_oif/
Regards,
Mohan Raj

The same error should appear in ST22. Run the transaction and locate this error entry. Then set an external break point at the statement before the dump and run the scenario in debug mode. You should be able to identify the error from there.

Abap mapping for content conditions routing in a flat-flat scenario

Dear Experts.
I have a flat-flat file scenario. Based on the content of the input file, I need to route data to the receiver.The source flat file will have several IDOC details.
Assume two fields FIELD1 and FIELD2 in different segments of the IDOC. My requirement is if FIELD1 of an IDOC = "XYZ" and FIELD2 of the same IDOC = "PQR", then this IDOC's details has to be passed to the receiver.
I have tried to implement the above condition at interface determination in graphical mapping.
In the graphical mapping, the problem is:
Assuming there are 3 idocs in the input file.
FIELD1 of IDOC[1] = 'XYZ' and FIELD2 of IDOC[1] = 'PQR'
FIELD1 of IDOC[2] = 'LMN' and FIELD2 of IDOC[2] = 'RST'
FIELD1 of IDOC[3] = 'ABC' and FIELD2 of IDOC[3] = 'DEF' .
Now, if none of the IDOCs in the input file satisfy my requirement,the message mapping should not be called at all. But in my case its failing because FIELD1 of IDOC[1] and FIELD2 of IDOC[3] together are satisfying the condition and hence the message mapping is getting called.
And I need to check this condition IDOC wise. Both the conditions has to be satisfied in the same IDOC.
The question is very similar to the one posted by SHOBHA HB. (Topic:Receiver determination(or Interface determination) and conditional routing )
but, due to complexities in the graphical mapping, we have decided to go for the ABAP mapping instead.
Kindly help, by mentioning the steps I should follow for this interface, the logic basically. I already have paths to some basic ABAP mapping documents from SDN, so, kindly refrain from posting general URLS for definition or history of ABAP mapping.
IF you could guide me on this interface, It would be really helpful.
regards,
giri raj

Hi,
/people/ravikumar.allampallam/blog/2005/02/10/different-types-of-mapping-in-xi
This document will help you to create ABAP Mapping .
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/3.0/how%20to%20use%20abap-mapping%20in%20xi%203.0.pdf
How to Use ABAP Mapping in Exchange Infrastructure 3.0 (NW2004)
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/5c46ab90-0201-0010-42bd-9d0302591383
SAP Network Blog: How to call XI ABAP Mapping via RFC
/people/ricardoandres.maienza/blog/2007/04/06/how-to-call-xi-abap-mapping-via-rfc
SAP Network Blog: Testing ABAP Mapping
/people/sameer.shadab/blog/2005/09/29/testing-abap-mapping
/people/udo.martens/blog/2006/08/23/comparing-performance-of-mapping-programs
An ad-on
/people/michal.krawczyk2/blog/2006/09/20/xi-abap-mapping-logs--more-standard-better-visibility
Regards

Transfer of legacy open P.O with attachments to SRM

Hello SRM Folks,
Can some one let me know How we can transfer Open P.O or closed P.O from Legacy system to SRM with Attachments directly..
Need your inputs..
Thanks in advance

Hi Ivy,
Thanks for the quick response. the note provided is for SRM 7.0 and SRM 7.0 EHP1 packages and currently we are in SRM 7.0 EHP2
Can you please guide me in configuring the settings required in DMS in ECC side.
1. Is it mandatory to use only document type of SRM in ECC or any Z-Document type can be used ?
2. Wat is the relevant settings to be mapped in DC10, DC20 and DC30 . If possible guide me step by step of settings for the document type to send the attachment in PR.
3. Does the system sends the document in URL or as an attachment to SC ?
Regards,
Ramprakash N

VPRS Condition amount varies in third party scenario.

Hi,
We all know that COST (VPRS condition value) in Invoice is fetched from MIRO in case of Third party sales scenario.
When we have 2 quantity in PO for a particular item, I have completed the MIRO(Vendor Invoicing) & VF01 (Customer Invoicing) for 1 quantity. Then the cost was reflecting in the document.
When I have created a new MIRO for the second quantity and cancelled the MIRO, system is updating the VPRS amount in already saved customer invoice to the extent of tax amount in the cancelled MIRO.
For Example:
PO Quantity - 2 for the material 'MAT12'
1st MIRO - Amount - 816000(incl of tax 16000)
Customer Invoice '123'- Cost (VPRS): 816000 (Initially shown)
2nd MIRO - Amount 816000(Incl of tax 16000)
And Cancelled this MIRO.
After cancelling, Customer Invoice '123' - Cost(VPRS) is 832000 (Got updated to the extent of tax amount in the cancelled MIRO).
CAN ANYONE PLS EXPLAIN WHY THIS UPDATION IN THE COST.
THANKS.
Guru

Good Morning,
For complete details on the behaviour of VPRS, please refer to the OSS Note 547570 (I have copied the relevant information below):
FAQ: VPRS in pricing
1. How is the cost determined in pricing?
    In the order, the cost is generally taken from the valuation segment
    of the material master. In the billing document, however, it may
    have other sources. Depending on the business transaction, the costs
    can be taken from the goods issue of the billed delivery or, in the
    case of a third-party order processing or individual purchase order,
    from the respective purchase order, the goods receipt or the invoice
    verification in purchasing. As an example, only the goods issue will
    be mentioned here. However, the descriptions also apply to costs
    from purchase orders, goods receipts or invoice verifications. For
    details, refer to Notes 372760 and 547590. These costs are entered
    externally in pricing and included in the value of the VPRS
    condition. The amount is obtained by calculating back amount = value
    / quantity.
4. How can I recognize how the cost was determined?
    Go to the detail display of the VPRS condition. If the condition
    control (KSTEU) is set to 'H', the cost was taken from the goods
    issue. If it set to 'A', it was redetermined from the valuation
    segment of the material master, in case of 'D' or 'E' it was copied
    from the preceding document.
7. Why is my VPRS not zero although my goods issue had value zero?
    For technical reasons, it is not possible within pricing to
    differentiate whether a goods issue with value zero exists or
    whether no goods issue exists. For this reason, in both cases the
    costs are determined from the valuation segment of the material
    master. In this context, also refer to Note 84229.
Here is some more useful documentation on VPRS.
u2022Configure VPRS with condition category G, S, or T
u2022Condition category G: the condition type VPRS goes into the valuation
segment of the material master and determines from here the standard
or
average price (based upon Price Control flag set in transaction MM03)
in the sales document.
In the billing document the value is determined from the post goods
issue document. When the post goods value = 0 the VPRS will be pulled
from the material valuation segment.
Regards,
Martina McElwain
SD - Forum Moderator

Conditional Calculations (IF-THEN-ELSE) - Simple Scenario

I am referring to the link below:
http://help.sap.com/saphelp_nw04/helpdata/en/23/17f13a2f160f28e10000000a114084/content.htm
For test purposes I have created a simple condition the details are below
( ( 'RKF1' <> 'Quantity Total Stock' ) OR ( 'RKF2' <> 'Quantity Total Stock' ) * 1 * 2 )
In my result set I would expect 1 to appear twice and 2 to appear once. However, I am only getting 1. why is this thanks?

Pradip,
this relates to Murali's post above, Murali provided this expression.
You wrote
+Case 1: Block 1 & Block 2 both are TRUE (Value 1)then
output = ((1)OR(1)12) = 112 = 2
Case 2: Both blocks are FALSE then
Output = ((0)OR(0)12) = 0
Case 3 : Block 1 is FALSE and Block 2 is TRUE then
Output = ((0)OR (1)12) = 112 = 2
Case 3 : Block 1 is TRUE and Block 2 is FALSE then
Output = ((1)OR (0)12) = 112 = 2+
Correct is
Case 1: Block 1 & Block 2 both are TRUE (Value 1)then
output = ((1)OR(1)12) = ((1) OR (2)) = 1</b>
Case 2: Both blocks are FALSE then
Output = ((0)OR(0)12) = 0
Case 3 : Block 1 is FALSE and Block 2 is TRUE then
Output = ((0)OR (1)12) = ((0) OR (2)) = 1
Case 3 : Block 1 is TRUE and Block 2 is FALSE then
Output = ((1)OR (0)12) = ((1) OR (1)) = 1</b>
You provided the correct reason yourself: <b>The result is 1 if <Expression1> or <Expression2> does not equal 0</b>. Otherwise the result is 0.
To achieve your results expression must be (note the brackets)
( ( 'RKF1' <> 'Quantity Total Stock' ) OR ( 'RKF2' <> 'Quantity Total Stock' ) ) *2
=======================================================
@Murali
I think I do know why a smart use of addition enables you to model a logical OR without using the boolean expression. But it does not work vice versa - logical OR never becomes an addition.
Best regards,
Björn
Message was edited by: Björn Grahlher

Condition types and Pricing in Contract management - SRM

Hello,
We have configured Contract management in SRM 5.0 (Global Outline Agreement).
I'm trying to create an exact rpelica of the R/3 pricing in SRM. Surprisingly when I created all condition types in SRM, it needs condition group maintenance. which in turn needs an access sequence. Now following are the problems I'm experiencing..
1. It is allowing to create a condition group maintenance in TTE. Somehow I managed it thru SPRO to create the one under BBP.
2. No menu path available to create a condition table under BBP. Again the same available for TTE. I managed to create this one as well.
3. Now the price/net price maintained at line item should get assigned to PB00 by default, but this does not get assigned.
4. All the documentation talks about implementation of BADI, but that does not help, cuz condition types may be created for new terms/norms in future.
Anyone has created condition types in SRM and implemented the same in Contract management and successfully replicated the contract in the backend with all condition types carried with values?
Regards,
Ashish

Hi
you check the bellow table for contacts data.
ekko--> Contract header data
ekpo--> Contract item data
konh--> Conditions header data
konp--> Conditions Item data
Regards
Anand

Join conditions in data source - Configurable sub scenario

Hello Experts,
In configurable sub scenario, when I try to join 2 tables (EKKO and EKPO), I am getting a warning message saying that "Redundant Join Conditions proposed; manual maintenance required" and the data source is not fetching any data.
Could anyone suggest what could be the reason
Regards,
Ramakrishna Chaitanya

Hello Ramakrishna,
Alessandro is right. EKKO-EBELN and EKPO-EBELN is the redundant condition. Just remove manually this row from the join condition and the warning message dissapears.
Best Regards,
Fernando

Transfer PO Conditions to R/3 in Extended Scenario (SRM 5.0)

Similar Messages

Maybe you are looking for