Conditions in Extended Szenario (SRM 5.0)

[Former Member]

Hi all,

we are using SRM 5.0 (SP09) in extended Szenario.

Everything works fine, purchase orders are transfered to R/3 with all information.

Unfortunately SAP standard does not support the conditions scheme in extended szenario, only the net price of a position is transfered to R/3.

For controlling reasons we would like to transfer the whole conditions scheme from SRM to R/3 as well, so you could see the price calculation with rebates etc. in the R/3 position as well.

Any ideas?

Points will be rewarded!

Thanks a lot

Regards

Andreas

[Former Member · Accepted solution]

Hi

Please go through the links below ->

P.S. - Conditions do not get transferred to backend. If you are working with ECS, this is a show stopper.

You can try to use *BBPECS_PO_OUT_BADI* to transfer this condition type to ECC. However, please check that the condition type from SRM do not apply again in ECC else your original price will be recalculated twice both in SRM and ECC..._

Hope this will help. Do let me know.

Regards

- Atul

[Former Member]

Problem resolved, thanks to all!

[Former Member]

Hi Andreas,

I am also having the same scenario. (PO: Transfer Conditions from SRM to R/3).

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 u have coding for this please suggest this will be very helpful for me.

Thanks and Regards,

Natchiappan.M

[Former Member]

Hi Andreas,

I am working on the similar scenario.

I need to transfer all condition types and related data to ECC?

I am using extended classics scenario , ECC 6, SRM 5.

Can you please guide me the steps for the same?

Thanks in advance.

Regards,

Hemant

[Ramki]

Hi Andreas

No need for modification.

Once you develop your own FM, Implement BBP_DRIVER_DETERMINE BADI to use your new function module instead of standard FM suggested by Yann.

Best regards

Ramki

[Former Member]

Hi Yann,

Hi Ramki,

thanks a lot so far!

I have implemented my own Z function mudule including the conditions scheme (pocond) for positions.

I have implemented the Badi BBP_DRIVER_DETERMINE, my new Z function module is called now-everything fine.

But I am stucked how to call "my FM" correctly?

I have tried to put in data for the pocond table but no conditions are transfered to my R/3, just the net price is transfered within my position.

I have put in data for the following fields:

gros price

ITM_NUMBER = no. of position in my PO (e.g. 00001)

COND_ST_NO = 001

COND_COUNT = 001 (depending on my calculation scheme in R/3)

COND_TYPE = PBXX (my gros price)

COND_VALUE = 100.000000000

CURRENCY = EUR

CURRENCY_ISO = EUR

APPLICATIO = M (for purchase)

CALCTYPCON = B

CHANGE_ID = U (Update)

rabates

ITM_NUMBER = no. of position in my PO (e.g. 00001)

COND_ST_NO = 001

COND_COUNT = 010 (depending on my calculation scheme in R/3)

COND_TYPE = Z05 (my gros price)

CON_VALUE = 10.000000000

CURRENCY = EUR

CURRENCY_ISO = EUR

APPLICATIO = M (for purchase)

CALCTYPCON = A

CHANGE_ID = U (Update)

I am sure that several fields are missing, does anyone has got a template how to fill in the condition data for the FM BBP_PO_INBOUND correctly?

Thanks a lot!

Best regards

Andreas

[Former Member]

Hi

Please go through the SAP Consulting OSS Notes as well ->

Note 1080875 PO: RFC call from SRM to backend is missing POPARTNER table

Note 1077978 Item text in PO is not transfered to backend

Note 718886 CUF. Transfer of user-defined fields of PO to backend

Note 636286 Customer fields are not transferred to R/3 Backend system

Note 1072114 Header text in PO is not transfered to backend

Hope this will help. Do let me know.

Regards

- Atul

[Former Member]

Hi Atul,

these notes do not solve the problem.

I have expanded the import params of standard FM BBP_PO_INBOUND with one table for conditions.

I just need some advise how to fill in my SRM conditions correctly into the new table so that R/3 is able to generate the conditions within my PO positions.

SO I tried to transfer a gross price, but only net price is transfered into my R/3 PO.

Any further ideas?

Best regards

Andreas

[Former Member]

Hi,

has anyone an idea how to fill in the import params for BBP_PO_INBOUND (conditions)?

Thanks for any hint!

Points will be rewarded!

Best gegards

Andreas

[yann_bouillut]

Hi andreas,

Here is my answer in a previous thread.

Yes you can definitely transfer SRM pricing condition to ECC.

This will involve badi BBP_DRIVER_DETERMINE.

Here are some hints from our SRM50 system.

You will have to copy function group ZBBP_BD_DRIVER_46A which will drive function modules ZB46B_DPO_TRANSFER and ZB46B_PO_CREATE.

You will have to enhance the ZB46B_DPO_TRANSFER with new tables

POCONDHEADER = lt_bapi_pocondheader

POCOND = lt_bapi_pocond

Then you will have to retrieve the SRM schema and condition price to fill in.

Good luck

Kind regards,

Yann

[Former Member]

Hi Atul,

Hi Yann,

thanks a lot for your answers, points have been rewarded so far.

@ Yann

Just to make it clear:

I have to copy FM B46B_DPO_TRANSFER into an own z-module, call this FM within a BADI implementation (BBP_DRIVER_DETERMINE) and implement the conditions schemes (tables) for header and positions and pass them with my values from SRM to R/3, right?

This FM will call standard FM BBP_PO_INBOUND in my ECC system and as far as I know, this FM is able to work with the conditions scheme (import params) - so no modification is necessary within this standard FM . I "just" have to enhance the SRM FM B46B_DPO_TRANSFER with the tables for my conditions schemes.

Am I right?

And last question: The standard FM in SRM for transfering PO within the extended Scenario is FM B46B_DPO_TRANSFER ? ( I did not have debugged this so far... )

Thanks a lot

Best Regards-> of course I will need some luck for that implementation!

Andreas

[yann_bouillut]

Hi Andreas,

Except if you have done others standard modifications to SRM PO, there are no header conditions in the standard SRM50 !

Thus, in standard, only item conditions can be sent to ECC.

Yes, you are correct there is nothing to do in bbp_po_inbound.

Only copy and modify B46B_DPO_TRANSFER .

B46B_DPO_TRANSFER is the FM i used between SRM50 and ECC60.

Kind regards,

Yann

[Former Member]

Thanks a lot Yann!!!

I will give you an update as soon as I have implemented my "modification"

Best regards

Andreas